Difference between revisions of "OpenID Connect"
From TMM Wiki
Jump to navigationJump to search| Line 3: | Line 3: | ||
}} | }} | ||
| − | As of version 4.1.21.1 NATS can be used as an OpenID Connect server. This is another option for member authentication. In order to utilize this feature, you will need to use an OpenID Connect client. When developing this feature, we used the [https://github.com/zmartzone/mod_auth_openidc mod_auth_openidc] apache module | + | As of version 4.1.21.1 NATS can be used as an OpenID Connect server. This is another option for member authentication. In order to utilize this feature, you will need to use an OpenID Connect client. When developing this feature, we used the [https://github.com/zmartzone/mod_auth_openidc mod_auth_openidc] apache module. Here is an [[Mod_auth_openidc|example]] implementation. |
== Initial NATS Setup == | == Initial NATS Setup == | ||
Revision as of 19:41, 1 August 2018
As of version 4.1.21.1 NATS can be used as an OpenID Connect server. This is another option for member authentication. In order to utilize this feature, you will need to use an OpenID Connect client. When developing this feature, we used the mod_auth_openidc apache module. Here is an example implementation.
Initial NATS Setup
- go to the NATS config admin -> surfers and scroll down to the 'Member OpenID Connect Server' section
- enable the ENABLE_MEMBER_OPENID config option
- provide a list of all ips defined on your member area server(s) by entering it into the MEMBER_OPENID_SECURE_IPS field
- enter the password your
