The authentication, authorization, and auditing traffic management feature now supports OAuth and OpenID-Connect mechanisms for authenticating and authorizing users to applications that are hosted on applications such as Google, Facebook, and Twitter.
The authentication mechanism facilitates the inline verification of OpenID tokens. The Citrix ADC appliance can be configured to obtain certificates and verify signatures on the token.
A major advantage of using the OAuth and OpenID-Connect mechanisms is that the user information is not sent to the hosted applications. Therefore, the risk of identity theft is considerably reduced.
The Citrix ADC appliance configured for authentication, authorization, and auditing now accepts incoming tokens that are signed using HMAC HS256 algorithm. In addition, the public keys of the SAML Identity Provider (IdP) are read from a file, instead of learning from a URL endpoint.
In the Citrix ADC implementation, the application is accessed by the authentication, authorization, and auditing traffic management virtual server. So, to configure OAuth, you must configure an OAuth policy which must then be associated with an authentication, authorization, and auditing traffic management virtual server.
OAuth on Citrix ADC appliance is qualified for all SAML IdPs that are compliant with “OpenID connect 2.0”.
To configure OAuth by using the configuration utility:
Configure the OAuth action and policy.
Navigate to Security > AAA - Application Traffic > Policies > Authentication > Advanced Policies > Policy, and create a policy with OAuth as the action type, and associate the required OAuth action with the policy.
Associate the OAuth policy with an authentication virtual server.
Navigate to Security > AAA - Application Traffic > Virtual Servers, and associate the OAuth policy with the authentication virtual server.
Attributes (1 to 16) can be extracted in the OAuth response. Currently these attributes are not evaluated. They are added for the future reference.
To configure OAuth by using the command line interface:
Define an OAuth action.
add authentication OAuthAction <name> -authorizationEndpoint <URL> -tokenEndpoint <URL> [-idtokenDecryptEndpoint <URL>] -clientID <string> -clientSecret <string> [-defaultAuthenticationGroup <string>][-tenantID <string>][-GraphEndpoint <string>][-refreshInterval <positive_integer>] [-CertEndpoint <string>][-audience <string>][-userNameField <string>][-skewTime <mins>][-issuer <string>][-Attribute1 <string>][-Attribute2 <string>][-Attribute3 <string>]...
Associate the action with an advanced authentication policy.
add authentication Policy** <name> -rule <expression> -action <string>
add authentication oauthAction a -authorizationEndpoint https://example.com/ -tokenEndpoint https://example.com/ -clientiD sadf -clientsecret df
For more information on authentication OAuthAction parameters, see authentication OAuthAction.
When a certEndpoint is specified, the Citrix ADC appliance polls that endpoint at the configured frequency to learn the keys. To configure a Citrix ADC to read the local file and parse keys from that file, a new configuration option is introduced as follows.
set authentication OAuthAction <> -**CertFilePath** <path to local file with jwks>
Name-value attribute support for OAuth authentication
You can now configure OAuth authentication attributes with a unique name along with values. The names are configured in the OAuth action parameter either as “Attributes” and the values are obtained by querying for the names. The extracted attributes are stored in authentication, authorization, and auditing session. Admins can query these attributes either using
http.req.user.attribute("attribute name") or
http.req.user.attribute(1), based on the chosen method of specifying attribute names.
By specifying the name of attribute, admins can easily search for the attribute value associated with that attribute name. Also, admins no longer have to remember the “attribute1 to attribute16” by its number alone.
In a OAuth command, you can configure a maximum of 64 attributes separated by comma with a total size less than 1024 bytes.
The session failure can be avoided if the total value size of “attribute 1 to attribute 16” and values of attributes specified in “Attributes” are not more than 10 KB.
To configure the name-value attributes by using the CLI
At the command prompt, type:
add authentication OAuthAction <name> [-Attributes <string>]
set authentication OAuthAction <name> [-Attributes <string>]
add authentication OAuthAction a1 –attributes "email,company" –attribute1 email
set authentication OAuthAction oAuthAct1 -attributes "mail,sn,userprincipalName"