Difference between revisions of "Radius Authentication"
From SME Server
Jump to navigationJump to searchm |
m |
||
| Line 5: | Line 5: | ||
Placeholder | Placeholder | ||
| + | ---- | ||
| + | The framework is already in place for radius. In order to use it please define the client host in hostnames and addresses. | ||
| + | |||
| + | Once you have done this then you need to define the shared radius key for that host. You can do this with the following command: | ||
| + | |||
| + | db hosts setprop {full hostname} RadiusKey {random string of characters} | ||
| + | signal-event remoteaccess-update | ||
| + | |||
| + | ex. | ||
| + | |||
| + | db hosts setprop wireless.mydomain.com RadiusKey abcdefg123456789 | ||
| + | signal-event remoteaccess-update | ||
| + | |||
| + | After this I'd go to the device defined by wireless.mydomain.com and point to the internal interface ip for the server and enter the same key. | ||
| + | ---- | ||
[[Category:Howto]] | [[Category:Howto]] | ||
Revision as of 06:21, 28 June 2017
Placeholder
The framework is already in place for radius. In order to use it please define the client host in hostnames and addresses.
Once you have done this then you need to define the shared radius key for that host. You can do this with the following command:
db hosts setprop {full hostname} RadiusKey {random string of characters} signal-event remoteaccess-update
ex.
db hosts setprop wireless.mydomain.com RadiusKey abcdefg123456789 signal-event remoteaccess-update
After this I'd go to the device defined by wireless.mydomain.com and point to the internal interface ip for the server and enter the same key.
