FAQs
Which operating systems and version are supported?
A 64-bit operating system (Windows, macOS, or Linux), with at least 4 GB of RAM. The supported version is goauthproxy 1.00.07.
Do I need the Config ID?
Yes. Remember the config ID from AdminX — it is required to run the Auth Proxy for RADIUS/LDAP and must be passed as the -u <uuid> parameter. The UUID and Config ID must match for the server to work.
How long do configuration changes take to apply?
The wait time for changes to take effect is 10 minutes.
What happens after I delete a configuration?
After removing the configuration, users cannot authenticate using the deleted Config ID.
Can a single GoAuthProxy instance run multiple LDAP/LDAPS servers at the same time?
No. A single GoAuthProxy instance does not currently support multiple LDAP/LDAPS servers simultaneously.
Do I need root access to run LDAP on low ports?
On Linux and macOS, root access is required to run servers on ports below 1024, including LDAP on port 389 and LDAPS on port 636.
Can I run RADIUS and LDAP together?
Yes. The -r parameter can be used together with the LDAP -l parameter; setting -r true starts the RADIUS server along with the LDAP server.
What are the default RADIUS port and secret?
The default RADIUS port is 1812 and the default secret is secret. The default secret should only be used for testing; production servers should always use a secure secret string.
What is the maximum length of the RADIUS shared secret?
The maximum length is 256 bytes, it is case sensitive, and a length of at least 16 characters is recommended.
How do I handle special characters in the RADIUS secret?
If the secret contains bash shell special characters ($, (, ), …), escape it so bash does not interpret the characters as shell commands — for example, secret$pecialchar(12).
Last updated
Was this helpful?

