oauth
Enables OAuth-driven Google and/or Facebook authentication on captive
portals that use internal Web pages.
To enable Google and Facebook captive-portal authentication:
- Enforce captive-portal authentication on the WLAN to which wireless-clients associate.
For information, see captive-portal-enforcement.
- Set captive-portal Web page location to internal. For more information, see webpage-location.
- Register your
captive-portal individually on Google/FaceBook APIs and generate a
client-id and client-secret. The client-ids retrieved during
registration are the IDs for the WiNG application running on the
access point/controller. The WiNG application uses these client-ids
to access the Google and Facebook Auth APIs, and authenticate the
guest client on behalf of the user.
If enabling OAuth-driven Google and/or Facebook authentication on the
captive portal, use this command to configure the Google/Facebook client-ids. Once enabled,
the captive portal landing page, displayed on the client‘s browser, provides the Facebook
and Google login buttons.
Supported in the following platforms:
- Access Points — AP505i, AP510i/e,
AP560i/h
- Service Platforms
— NX5500, NX7500, NX9500, NX9600, VX9000
Syntax
oauth
oauth client-id [facebook|google] <WORD>
Parameters
oauth
| oauth |
Execute this command without the associated keywords to
enable OAuth on this captive-portal. If enabling OAuth, ensure the captive-portal
Web page location is configured as advanced or external. |
|
oauth client-id [facebook|google] <WORD>
| oauth client-id [facebook|google] <WORD> |
Configures the client-ids retrieved from the Google and
Facebook API manager portals during registration
- facebook –
Configures the Facebook API client-id (is a 15 digit
entity)
- google –
Configures the Google API client-id (is a 12 digit
number)
- <WORD> – Provide the Facebook/Google
client-id.
If the captive-portal Web page location is advanced or
external, and you are enabling OAuth support, you need not
configure the client-id. In such a scenario, the client-id is
configured through the EGuest server UI and not the WiNG
CLI.
|
|
Example (User Exec Mode)
nx7500-6DCD39(config-captive-portal-test2)#OAuth
nx7500-6DCD39(config-captive-portal-test2)#OAuth client-id Google xxxxxxxxxxxx.apps.googleusercontent.com Facebook yyyyyyyyyyyyyyy
nx7500-6DCD39(config-captive-portal-test2)#show context
captive-portal test2
server host guest.social.com
oauth
oauth client-id Google xxxxxxxxxxxx.apps.googleusercontent.com Facebook yyyyyyyyyyyyyyy
nx7500-6DCD39(config-captive-portal-test)#
In the above example,
- xxxxxxxxxxxx - Is the 12 digit numeric part of your Google client-id.
- yyyyyyyyyyyyyyy - Is the 15 digit Facebook client-id
Related Commands
| no |
Removes all OAuth client identities configured for this
captive portal |
|
Print
this page
Email this topic
Feedback
View PDF
Download EPUB