OIDC Class

Properties   Methods   Events   Config Settings   Errors  

The OIDC class provides an easy way to add OpenID Connect based SSO to your application.

Syntax

cloudsso.OIDC

Remarks

The OIDC class provides a simple way to authenticate users using OpenID Connect. The library makes it easy to add SSO support to web applications. Identity management is performed by OpenID Providers such as Microsoft, Google, Apple, GitHub, GitLab, Okta, or others.

An application that uses an OpenID Provider for authentication purposes is referred to as a Relying Party. When a user visits a website (Relying Party) they are directed to authenticate with the chosen OpenID Provider. Once authenticated, the user will give the OpenID Provider consent to use their account information to login to the Relying Party's service. The Relying Party will then be issued an ID Token by the OpenID Provider that will then be verified to confirm the identity of the user. This removes the need to manage and secure a user's sensitive information like passwords. Additionally, an OpenID Provider can also provide profile information about the user, further reducing the amount of information that needs to be stored.

Setup

Typically, the Relying Party will need to register their application with the OpenID Provider. This will give the OpenID Provider knowledge about the Relying Party. The exact information needed depends on the OpenID Provider that is being used but typically this will include the redirect_uri that users will be returned to after authentication has been completed. Once registered, the OpenID Provider will also provide the Relying Party with some information. Typically the following values will be provided by the OpenID Provider:

• Client Id (Required)
• Client Secret (Optional)
• Discovery Document URL (Recommended)

Once the application has been registered, the Relying Party can begin authenticating users.

Discovery

To start, a Relying Party will need to get information about the OpenID Provider they are connecting to. OIDC uses discovery documents to provide information about an OpenID Provider to a Relying Party. The OpenID Provider should host their discovery document at the domain of the issuer with /.well-known/openid-configuration concatenated at the end. For example, if the issuer is https://example.com then the discovery document URL would be:

https://example.com/.well-known/openid-configuration

This document stores important information that is required to correctly make requests and validate responses from an OpenID Provider.

Usage: Getting the Discovery Document

The OIDC class simplifies requesting and parsing the discovery document. The RequestDiscoveryDoc method will make a request to the specified discovery document URL. It will retrieve the discovery document and parse the commonly used information from it, setting the fields in the DiscoveryDocDetails property. For example:

oidc.RequestDiscoveryDoc("https://example.com/.well-known/openid-configuration"); string issuer = oidc.DiscoveryDocDetails.Issuer;

This discovery document does change from time to time but typically it can be cached to reduce the number of requests being made by the relying party. To save the discovery document for later, the Content field can be queried to get the raw JSON document. When the discovery document needs to be reloaded, the LoadDiscoveryDoc method can be used to reload the document. For example:

oidc.RequestDiscoveryDoc("https://example.com/.well-known/openid-configuration"); string raw_document = oidc.DiscoveryDocDetails.Content; //Save raw_document for later oidc.LoadDiscoveryDoc(raw_document);

The following properties and methods handle requesting, loading, or parsing discovery documents:

• DiscoveryDocDetails
• GetDiscoveryMetadata
• LoadDiscoveryDoc
• RequestDiscoveryDoc

Signing Certificates

The discovery document also provides a URI for the JSON Web Key Set or (JWKS) that will be used to verify ID Tokens (see below). Each JSON Web Key Set contains one or more public certificates (keys) that correspond to a private key that can be used when an OpenID provider signs an ID Token. These keys are often rotated periodically but can generally be cached to reduce the amount of requests being made by the Relying Party.

Usage: Requesting and Reloading Signing Certificates

The RequestSignerCerts method can be used to request the JWKS directly from the JWKS URI. This method will set the SignerJWKS which is automatically parsed to fill the SignerCerts collection. If the SignerCerts collection is empty and the class needs to verify the ID Token, the class will automatically make this request.

To reduce the number of requests made by the Relying Party, the LoadSignerJWKS method can be used to parse the SignerJWKS property again. This allows the Relying Party to cache the SignerJWKS property and reuse it later. This can reduce the amount of times the JWKS is requested from the OpenID Provider. oidc.RequestDiscoveryDoc("https://example.com/.well-known/openid-configuration"); oidc.RequestSignerCerts(); string raw_jwks = oidc.SignerJWKS; //Save or Cache for later. //Continue on with operations that need to verify an ID Token. //Sometime later with a new instance. oidc.SignerJWKS = raw_jwks; oidc.LoadSignerJWKS(); //Continue on with new operations that need to verify an ID Token.

Authentication

The exact flow that a Relying Party goes through to authenticate a user depends on how the Relying Party configures their requests. These flows are broken up into different Grant Types with the most common being the Authorization Code grant type.

For a Relying Party using the Authorization Code grant type, the user must be redirected to the OpenID Provider's Authorization URL. The OpenID Provider will first ask the user to authenticate themselves. Once the user is authenticated, the OpenID Provider will then request authorization from the user to allow the Relying Party to access specific information about their account. This information will then be used to authenticate the user to the Relying Party. Once authorization has been provided, the user will be redirect back to the Relying Party with an authorization code.

With the authorization code, the Relying Party can now make a request to the token URL. The token server requires the authorization_code, client_id and optional client_secret to confirm that the Relying Party has gotten authorization from the authorization server. The token server will then return an access_token,id_token, and optional refresh_token. To finish authenticating the user to the web application, the Relying Party will then validate the ID Token (see below).

Getting Authorization

Usage: Getting the Authorization URL

The following example will assume that the Relying Party is using the ogtAuthorizationCode GrantType. This grant type sets the ResponseType to code instructing the OpenID Provider to send the authorization code once authorization has been completed. First, the OIDC class needs to be configured with the information about the OpenID Provider (see Discovery above) and the specific information that has been provided or configured about the Relying Party. Once the component is configured, the GetAuthorizationURL method can be used to get the URL that the user should be directed to in order to complete the authorization process. //OpenID Provider oidc.RequestDiscoveryDoc("https://example.com/.well-known/openid-configuration"); //Relying Party oidc.GrantType = ogtAuthorizationCode; oidc.ClientId = "Relying Party ID" ; oidc.ReturnURL = "https://relying_party.com/"; oidc.AuthorizationScope = "openid profile email"; string authorization_url = oidc.GetAuthorizationURL(); //Direct the user to the URL...

Authorization Response

Parse vs. Process

The ParseHTTPRequest and ProcessHTTPRequest methods are used to handle HTTP requests. Generally, unless additional considerations or control is needed, the ProcessHTTPRequest method should be used. ProcessHTTPRequest will parse the incoming request and make any additional requests necessary to obtain the access tokens and ID Tokens, as well as perform any necessary validation. For example, if an authorization code is found in the request, it will automatically make a requests to the token server and handle/validate the response.

The ParseHTTPRequest method will only parse the information from the request. If an ID Token is found in the request, it will be validated. No further actions are performed.

Usage: Handling a redirect from an OpenID Provider

The OIDC class provides the ParseHTTPRequest and ProcessHTTPRequest methods to make it simple to get the required information from a redirect. By default these methods will attempt to read the HTTP request headers and body from the specified HttpServletRequest object.

If the current HTTP context is unavailable, for instance when the class is not used directly within a web application, the HTTP headers and body can be supplied by setting the HTTPRequestHeaders and HTTPRequest properties.

The rest of the examples in this section will assume that the ParseHTTPRequest method is being used. See the ProcessHTTPRequest method for more information.

Getting Tokens

When RequestTokens is called a request is made to the token server. The token server authenticates the requester (the Relying Party) using the information provided in the request. Then, the token server will return an access token, an ID Token, and an optional refresh token. The Relying Party then needs to verify the ID Token (see below).

Refresh Tokens

Refresh tokens allow Relying Parties to skip obtaining authorization again for users that have already provided it once. How refresh tokens work depends on the OpenID Provider but when the RefreshToken property is set before calling RequestTokens the request will be made without the authorization code, using the RefreshToken instead.

Usage: Request Tokens

The RequestTokens method is used in the following example to make a request to the Token server after ParseHTTPRequest has been called. //Parse HTTP Request oidc.ParseHTTPRequest(); //Get OpenID Provider Settings oidc.RequestDiscoveryDoc("https://example.com/.well-known/openid-configuration"); //Relying Party Settings oidc.GrantType = ogtAuthorizationCode; oidc.ClientId = "Relying Party ID" ; oidc.ClientSecret = "Relying Party Secret Value" ; oidc.ReturnURL = "https://relying_party.com/"; oidc.AuthorizationScope = "openid profile email"; try{ oidc.RequestTokens(); } catch (OIDCException e){ //Error handling if there is an issue with the response. } string access_token = oidc.AccessToken; string id_token = oidc.IdTokenInfo.IdTokenContent; string refresh_token = oidc.RefreshToken;

Verifying ID Tokens

When a Relying Party receives an ID Token, it can verify the token to confirm the identity of the user that it represents. When the class receives an ID Token after calling ParseHTTPRequest, ProcessHTTPRequest, or RequestTokens it will automatically validate the ID Token.

The validation process checks the different JWT claims in the ID Token along with the signature using one of the keys from the JWKS provided by the OpenID Provider (see Signing Certificates). The following claims are used to validate the ID Token:

Usage: Validate an ID Token

In a case where an ID Token is provided directly to the class, the ValidateIdToken can be used to parse and validate it. The following example will setup the class with the information needed to validate the ID Token. //OpenID Provider oidc.RequestDiscoveryDoc("https://example.com/.well-known/openid-configuration"); oidc.RequestSignerCerts(); //Relying Party oidc.ClientId = "Relying Party ID" ; oidc.IdTokenInfo.IdTokenContent = "ID_TOKEN"; try{ oidc.ValidateIdToken(); } catch (OIDCException e){ //If there is any validation issues. } //Continue with the validated ID Token.

User Information

OpenID Providers give information about users through claims. These claims can be found in an ID Token or by calling the UserInfo endpoint to request the information directly.

When commonly used claims are parsed from an ID Token or the response from the UserInfo endpoint, the class will set the fields in the UserDetails property with the corresponding information. If there is a claim that is not found in the UserDetails property, then the GetIdTokenClaim and the GetUserInfoClaim methods can be used to search for specific claims.

Usage: Request UserInfo

To make a request to the UserInfo endpoint, the class will need to have the AccessToken property set. Additionally, the Discovery Document can be used to get the UserInfo endpoint. The following code example assumes that the AccessToken has been set to a cached token from the current user session. oidc.RequestDiscoveryDoc("https://example.com/.well-known/openid-configuration"); oidc.AccessToken = "ACCESS_TOKEN" ; oidc.RequestUserInfo(); string email = oidc.UserDetails.Email; string custom_claim = oidc.GetUserInfoClaim("/json/custom_claim");

Property List

The following is the full list of the properties of the class with short descriptions. Click on the links for further details.

Method List

The following is the full list of the methods of the class with short descriptions. Click on the links for further details.

Event List

The following is the full list of the events fired by the class with short descriptions. Click on the links for further details.

Config Settings

The following is a list of config settings for the class with short descriptions. Click on the links for further details.

AccessToken Property (OIDC Class)

The access token received from an OpenID provider.

Syntax

public String getAccessToken();


public void setAccessToken(String accessToken);

Default Value

""

Remarks

This property will be populated with an access token that was received from an OpenID provider. When set the AccessTokenExp configuration setting will also be set with the expiration date of the access token. The access token allows for requests to be made to the UserInfoURL to retrieve information about the authenticated user. Additionally, depending on the OpenID provider, it may be used to access other APIs that are supported by the OpenID provider depending on how AuthorizationScope was set when calling GetAuthorizationURL.

Each AccessToken is specific to the user that authorized the OpenID provider to provide it to your application. An AccessToken cannot be shared between multiple users.

When an OpenID provider provides an access token depends on the ResponseType that was set when calling GetAuthorizationURL. Typically, the ResponseType configuration setting is set when selecting a GrantType which is default set to ogtAuthorizationCode. When ResponseType contains code (ogtAuthorizationCode and ogtHybrid) then the AccessToken is provided by the TokenURL. When ResponseType contains token (ogtAuthorizationCode and ogtHybrid) then the AccessToken is provided by the AuthorizationURL.

AuthorizationScope Property (OIDC Class)

The authorization scope used during authorization.

Syntax

public String getAuthorizationScope();


public void setAuthorizationScope(String authorizationScope);

Default Value

"openid"

Remarks

This property specifies the authorization scopes sent in the authorization request. The value specified here must be a space separated list of scopes. For instance openid profile email. The openid scope is always required to be present. The default value is openid.

After calling ProcessHTTPRequest or ParseHTTPRequest, if the authorization server returned the scope parameter, this property will be updated to match.

Along with OpenID Connect scopes, some OpenID providers also support other OAuth 2.0 scopes for various APIs that are also hosted by the OpenID provider. These can often also be added alongside the OpenID scopes. For example, openid profile email offline_access Mail.ReadWrite would be an example of a valid AuthorizationScope when using Microsoft Entra as an OpenID provider.

See the OpenID provider's documentation for supported values.

AuthzResponseCode Property (OIDC Class)

The error code from a recently parsed HTTP request.

Syntax

public String getAuthzResponseCode();

Default Value

""

Remarks

The most recent error response code from a HTTP request that contains the response to an authorization (Authz) attempt. This is set when calling the ParseHTTPRequest or ProcessHTTPRequest and the error response parameter is present. A description (if provided) of the error code can be found in the AuthzResponseDesc property. The AuthErrorURI configuration setting may also be set if the request provided a URL to a page that describes the error.

This property is read-only.

AuthzResponseDesc Property (OIDC Class)

The error description from a recently parsed HTTP request.

Syntax

public String getAuthzResponseDesc();

Default Value

""

Remarks

The most recent error response description from a HTTP request that contains the response to an authorization (Authz) attempt. This is set when calling the ParseHTTPRequest or ProcessHTTPRequest and the error_description response parameter is present. The code for this error can be found in the AuthzResponseCode property.

This property is read-only.

ClientId Property (OIDC Class)

The Id of the client assigned when registering the application.

Syntax

public String getClientId();


public void setClientId(String clientId);

Default Value

""

Remarks

This property holds the Id of the client that was assigned when initially registering the application with the OpenID provider. This is sometimes referred to as the application id or the relying party id. This property is used to build the authorization URL when calling GetAuthorizationURL. It is also used when making a request to the token server when calling ProcessHTTPRequest and RequestTokens. Additionally, it is used to verify the Audience field when verifying an ID Token when calling the ValidateIdToken, ProcessHTTPRequest, and possibly RequestTokens methods.

ClientSecret Property (OIDC Class)

The secret value for the client assigned when registering the application.

Syntax

public String getClientSecret();


public void setClientSecret(String clientSecret);

Default Value

""

Remarks

This property holds the secret of the client that might have been assigned when initially registering the application with the OpenID provider. This property is optional depending on the OpenID provider. If provided, it will be used when making a request to the token server when calling RequestTokens or ProcessHTTPRequest.

Connected Property (OIDC Class)

This property shows whether the class is connected.

Syntax

public boolean isConnected();

Default Value

False

Remarks

This property is used to determine whether or not the class is connected to the remote host. Use the Connect and Disconnect methods to manage the connection.

This property is read-only and not available at design time.

Cookies Property (OIDC Class)

This property includes a collection of cookies.

Syntax

public HTTPCookieList getCookies();


public void setCookies(HTTPCookieList cookies);

Remarks

This property contains a collection of cookies. To add cookies to outgoing HTTP requests, add cookies (of type HTTPCookie) to this collection.

To see cookies that are set by the server, use the SetCookie event, which displays the cookies and their properties as set by the server. Those cookies also are added to Cookies.

MaxHTTPCookies can be used to control the maximum number of cookies saved.

This collection is indexed from 0 to size -1.

This property is not available at design time.

DiscoveryDocDetails Property (OIDC Class)

Details about the OpenID provider's discovery document.

Syntax

public DiscoveryDocDetails getDiscoveryDocDetails();

Remarks

This property holds details parsed from the discovery document after GetDiscoveryDoc is called. See GetDiscoveryDoc for more details.

This property holds details parsed from the discovery document after RequestDiscoveryDoc or LoadDiscoveryDoc is called.

This property is read-only and not available at design time.

Firewall Property (OIDC Class)

A set of properties related to firewall access.

Syntax

public Firewall getFirewall();


public void setFirewall(Firewall firewall);

Remarks

This is a Firewall-type property, which contains fields describing the firewall through which the class will attempt to connect.

FollowRedirects Property (OIDC Class)

This property determines what happens when the server issues a redirect.

Syntax

public int getFollowRedirects();


public void setFollowRedirects(int followRedirects);


Enumerated values:
  public final static int frNever = 0;
  public final static int frAlways = 1;
  public final static int frSameScheme = 2;

Default Value

0

Remarks

This property determines what happens when the server issues a redirect. Normally, the class returns an error if the server responds with an "Object Moved" message. If this property is set to frAlways (1), the new URL for the object is retrieved automatically every time.

If this property is set to frSameScheme (2), the new URL is retrieved automatically only if the URLScheme is the same; otherwise, the class throws an exception.

Note: Following the HTTP specification, unless this property is set to frAlways (1), automatic redirects will be performed only for GET or HEAD requests. Other methods potentially could change the conditions of the initial request and create security vulnerabilities.

Furthermore, if either the new URL server or port are different from the existing one, User and Password are also reset to empty. If, however, this property is set to frAlways (1), the same credentials are used to connect to the new server.

A Redirect event is fired for every URL the product is redirected to. In the case of automatic redirections, the Redirect event is a good place to set properties related to the new connection (e.g., new authentication parameters).

The default value is frNever (0). In this case, redirects are never followed, and the class throws an exception instead.

GrantType Property (OIDC Class)

The grant type defining the authentication flow.

Syntax

public int getGrantType();


public void setGrantType(int grantType);


Enumerated values:
  public final static int ogtAuthorizationCode = 0;
  public final static int ogtImplicit = 1;
  public final static int ogtHybrid = 2;

Default Value

0

Remarks

This property defines the grant type used when performing authentication. The value specified here controls the authentication flow.

Possible values for GrantType are:

• 0 (Authorization Code - Default)
• 1 (Implicit)
• 2 (Hybrid)

When handled by the class using the ParseHTTPRequest and ProcessHTTPRequest methods each grant type acts in the following manner by default.

When using 0 (Authorization Code Flow - Default), the AuthorizationCode configuration setting is set by the authorization server . When using ProcessHTTPRequest or calling the RequestTokens method after parsing, the class will make a request to the token server and return an AccessToken and IdTokenInfo properties. If provided, this grant type also supports the RefreshToken property.

When using 1 (Implicit Flow), the AccessToken and IdTokenInfo properties are set by the authorization server. This is only recommended for implementations that are in-browser, as this potentially exposes the tokens to the end-user and user agent itself.

When using 2 (Hybrid Flow), by default the AuthorizationCode configuration setting is set by the authorization server along with the IdTokenInfo property (see Additional Notes). When using ProcessHTTPRequest or calling the RequestTokens method after parsing, the class will make a request to the token server and set the AccessToken property and if provided again the IdTokenInfo property. If provided, this grant type also supports the RefreshToken property.

Additional Notes

The response_type request parameter is automatically set based on the value specified here. In some cases multiple values are acceptable and a default value is chosen automatically. To explicitly specify a response_type value for the chosen grant type set ResponseType after setting this property.

HTTPRequest Property (OIDC Class)

The HTTP body of a request.

Syntax

public String getHTTPRequest();


public void setHTTPRequest(String HTTPRequest);

Default Value

""

Remarks

The HTTP body for a request. This can be set to directly provide the HTTP body to be processed for the ParseHTTPRequest or ProcessHTTPRequest methods. This property is also set with the HTTP body that are parsed from the HTTP context.

HTTPRequestHeaders Property (OIDC Class)

The HTTP headers of a request.

Syntax

public String getHTTPRequestHeaders();


public void setHTTPRequestHeaders(String HTTPRequestHeaders);

Default Value

""

Remarks

The HTTP headers for a request. This can be set to directly provide the HTTP headers to be processed for the ParseHTTPRequest or ProcessHTTPRequest methods. This property is also set with the HTTP headers that are parsed from the HTTP context.

Idle Property (OIDC Class)

This property specifies the current status of the class.

Syntax

public boolean isIdle();

Default Value

True

Remarks

Idle will be False if the component is currently busy (communicating or waiting for an answer), and True at all other times.

This property is read-only.

IdTokenInfo Property (OIDC Class)

Information about the current ID Token.

Syntax

public IdTokenInfo getIdTokenInfo();

Remarks

This property holds details about the ID Token.

When an ID Token is validated either by calling ValidateIdToken or when it is retrieved after calling ProcessHTTPRequest or RequestTokens this property is populated with the claims that are specific to the ID Token.

This property is read-only and not available at design time.

LocalHost Property (OIDC Class)

This property includes the name of the local host or user-assigned IP interface through which connections are initiated or accepted.

Syntax

public String getLocalHost();


public void setLocalHost(String localHost);

Default Value

""

Remarks

The LocalHost property contains the name of the local host as obtained by the gethostname() system call, or if the user has assigned an IP address, the value of that address.

In multihomed hosts (machines with more than one IP interface) setting LocalHost to the IP address of an interface will make the class initiate connections (or accept in the case of server classs) only through that interface. It is recommended to provide an IP address rather than a hostname when setting this property to ensure the desired interface is used.

If the class is connected, the LocalHost property shows the IP address of the interface through which the connection is made in internet dotted format (aaa.bbb.ccc.ddd). In most cases, this is the address of the local host, except for multihomed hosts (machines with more than one IP interface).

Note: LocalHost is not persistent. You must always set it in code, and never in the property window.

OtherHeaders Property (OIDC Class)

This property includes other headers as determined by the user (optional).

Syntax

public String getOtherHeaders();


public void setOtherHeaders(String otherHeaders);

Default Value

""

Remarks

This property can be set to a string of headers to be appended to the HTTP request headers created from other properties like ContentType and From.

The headers must follow the format Header: Value as described in the HTTP specifications. Header lines should be separated by CRLF ("\r\n") .

Use this property with caution. If this property contains invalid headers, HTTP requests may fail.

This property is useful for extending the functionality of the class beyond what is provided.

This property is not available at design time.

Params Property (OIDC Class)

The parameters to be included in the request to the authorization server or received in the response.

Syntax

public OAuthParamList getParams();


public void setParams(OAuthParamList params);

Remarks

This is a collection of query string parameters to be added in the request when creating the authorization URL. This will also hold the parameters returned in the response.

This property is not available at design time.

Proxy Property (OIDC Class)

A set of properties related to proxy access.

Syntax

public Proxy getProxy();


public void setProxy(Proxy proxy);

Remarks

This property contains fields describing the proxy through which the class will attempt to connect.

RefreshToken Property (OIDC Class)

The refresh token received from or sent to the token server.

Syntax

public String getRefreshToken();


public void setRefreshToken(String refreshToken);

Default Value

""

Remarks

The class sets this property when it receives a RefreshToken after the ProcessHTTPRequest or RequestTokens methods makes a request to an OpenID provider's token server.

Usage:

In cases where a user's session may last longer than the actual expiration period (see AccessTokenExp) for the user's AccessToken the RefreshToken can be used to "refresh" the session. "Refreshing" the session allows the application to get a new access token without needing to have the user re-authorize the application again. To have the *prodtype; use a RefreshToken, first the application will need to save the refresh token in a secure location. RefreshToken are specific to the user meaning each user will need to have their own RefreshToken saved. Once the application needs a new AccessToken it will just set this property before calling the RequestTokens method.

Some OpenID providers will also return a newly issued ID Token when using a RefreshToken to get a new AccessToken. Additionally, some OpenID providers will either provide a new RefreshToken or reset the expiration date on the RefreshToken that was used. See the OpenID provider's documentation for more specifics.

ReturnURL Property (OIDC Class)

The URL where the user (browser) returns after authorization.

Syntax

public String getReturnURL();


public void setReturnURL(String returnURL);

Default Value

""

Remarks

The URL that is used by the authorization server to redirect the user after the user has finished the authorization process with the authorization server. This property corresponds to the redirect_uri query string parameter when GetAuthorizationURL creates the authorization URL.

Typically, this is set to the part of the web server that is responsible for processing incoming HTTP requests using the ProcessHTTPRequest or ParseHTTPRequest methods.

SignerCerts Property (OIDC Class)

The signing certificates from an OpenID provider.

Syntax

public CertificateList getSignerCerts();

Remarks

A list of certificates from the OpenID provider that are used for signing ID Tokens. This collection can be manually populated using the RequestSignerCerts or LoadSignerJWKS methods.

The collection can be automatically populated when needed if it is empty and a SignerCertURL is available. This can happen when calling ParseHTTPRequest or ProcessHTTPRequest if the response type includes id_token, when calling RequestTokens or ProcessHTTPRequest if the token server returns an ID Token, or when calling ValidateIdToken.

This property is read-only and not available at design time.

SignerJWKS Property (OIDC Class)

JSON Web Key Set provided by an OpenID provider.

Syntax

public String getSignerJWKS();

Default Value

""

Remarks

The JSON Web Key Set provided by the OpenID Provider that will be used for signing id_tokens.

Typically, this is returned from the SignerCertURL when the class makes a request to populate the SignerCerts collection. The RequestSignerCerts method can be used to manually make a request to the SignerCertURL or the class will automatically make the request if the collection is not set and it needs the certificates to validate an id_token.

This property can be saved/cached for later and used to reload the certificates by calling the LoadSignerJWKS method. This can be used to reduce how often the component makes request to the SignerCertURL server.

This property is read-only.

SSLAcceptServerCert Property (OIDC Class)

This property instructs the class to unconditionally accept the server certificate that matches the supplied certificate.

Syntax

public Certificate getSSLAcceptServerCert();


public void setSSLAcceptServerCert(Certificate SSLAcceptServerCert);

Remarks

If it finds any issues with the certificate presented by the server, the class will normally terminate the connection with an error.

You may override this behavior by supplying a value for SSLAcceptServerCert. If the certificate supplied in SSLAcceptServerCert is the same as the certificate presented by the server, then the server certificate is accepted unconditionally, and the connection will continue normally.

Note: This functionality is provided only for cases in which you otherwise know that you are communicating with the right server. If used improperly, this property may create a security breach. Use it at your own risk.

SSLCert Property (OIDC Class)

This property includes the certificate to be used during Secure Sockets Layer (SSL) negotiation.

Syntax

public Certificate getSSLCert();


public void setSSLCert(Certificate SSLCert);

Remarks

This property includes the digital certificate that the class will use during SSL negotiation. Set this property to a valid certificate before starting SSL negotiation. To set a certificate, you may set the Encoded field to the encoded certificate. To select a certificate, use the store and subject fields.

SSLProvider Property (OIDC Class)

This property specifies the Secure Sockets Layer/Transport Layer Security (SSL/TLS) implementation to use.

Syntax

public int getSSLProvider();


public void setSSLProvider(int SSLProvider);


Enumerated values:
  public final static int sslpAutomatic = 0;
  public final static int sslpPlatform = 1;
  public final static int sslpInternal = 2;

Default Value

0

Remarks

This property specifies the SSL/TLS implementation to use. In most cases the default value of 0 (Automatic) is recommended and should not be changed. When set to 0 (Automatic), the class will select whether to use the platform implementation or the internal implementation depending on the operating system as well as the TLS version being used.

Possible values are as follows:

In most cases using the default value (Automatic) is recommended. The class will select a provider depending on the current platform.

When Automatic is selected, the platform implementation is used by default. When TLS 1.3 is enabled via SSLEnabledProtocols, the internal implementation is used.

SSLServerCert Property (OIDC Class)

This property includes the server certificate for the last established connection.

Syntax

public Certificate getSSLServerCert();

Remarks

SSLServerCert contains the server certificate for the last established connection.

SSLServerCert is reset every time a new connection is attempted.

This property is read-only.

State Property (OIDC Class)

Opaque value used to maintain state between the request and response.

Syntax

public String getState();


public void setState(String state);

Default Value

""

Remarks

This property optionally holds a string value which will be returned by the authorization server with the response.

Any value may be specified here and it will be returned exactly as it was sent. This can be used to maintain state within the application, and also may be used for security purposes (for instance to prevent Cross-Site Request Forgery). The contents of this property are treated as an opaque value.

Timeout Property (OIDC Class)

This property includes the timeout for the class.

Syntax

public int getTimeout();


public void setTimeout(int timeout);

Default Value

60

Remarks

If the Timeout property is set to 0, all operations will run uninterrupted until successful completion or an error condition is encountered.

If Timeout is set to a positive value, the class will wait for the operation to complete before returning control.

The class will use DoEvents to enter an efficient wait loop during any potential waiting period, making sure that all system events are processed immediately as they arrive. This ensures that the host application does not freeze and remains responsive.

If Timeout expires, and the operation is not yet complete, the class throws an exception.

Note: By default, all timeouts are inactivity timeouts, that is, the timeout period is extended by Timeout seconds when any amount of data is successfully sent or received.

The default value for the Timeout property is 60 seconds.

TransferredData Property (OIDC Class)

The contents of the last response from the server.

Syntax

public byte[] getTransferredData();

Default Value

""

Remarks

This property contains the contents of the last response from the server.

TransferredDataLimit controls the maximum amount of data accumulated in TransferredData (by default, there is no limit).

This property is read-only and not available at design time.

TransferredHeaders Property (OIDC Class)

This property includes the full set of headers as received from the server.

Syntax

public String getTransferredHeaders();

Default Value

""

Remarks

This property returns the complete set of raw headers as received from the server.

The Header event shows the individual headers as parsed by the class.

This property is read-only and not available at design time.

UsePKCE Property (OIDC Class)

Whether Proof Key for Code Exchange (PKCE) should be used.

Syntax

public boolean isUsePKCE();


public void setUsePKCE(boolean usePKCE);

Default Value

False

Remarks

If specified, Proof Key for Code Exchange (PKCE) defined by RFC 7636 will be used when GetAuthorizationURL is called. This applies when GrantType is set to the Authorization Code or Hybrid grant types. Typically, a new instance of the class will be used to process the request from the authorization server than the one used to create the request to the authorization server. To verify the request from the authorization server, the PKCEVerifier will need to be saved in a safe location. Then before handling the request from the authorization server, the PKCEVerifier should be set to the saved value.

UserDetails Property (OIDC Class)

The claims about the user.

Syntax

public UserDetails getUserDetails();

Remarks

This property holds details about the user.

When an ID Token is validated either by calling ValidateIdToken or when it is retrieved after calling ProcessHTTPRequest or RequestTokens this property is populated with the claims from the ID Token.

When RequestUserInfo is called this property is populated from the returned claims.

This property is read-only and not available at design time.

AddCookie Method (OIDC Class)

This method adds a cookie and the corresponding value to the outgoing request headers.

Syntax

public void addCookie(String cookieName, String cookieValue);

Remarks

This property adds a cookie and the corresponding value to the outgoing request headers. Please refer to the Cookies property for more information on cookies and how they are managed.

AddParam Method (OIDC Class)

Adds a name-value pair to the query string parameters of the outgoing request.

Syntax

public void addParam(String paramName, String paramValue);

Remarks

This method can be used to add query string parameters to the requests being built by the GetAuthorizationURL method.

For example this can be used to set the ui_locales request parameter. This parameter allows for you to provide language preferences to the authorization server for a more cohesive user experience. For example the following example informs the authorization server that the user would prefer French (Canada), French (General), and English (General) in that order.

oidc.AddParam("ui_locales", "fr-CA fr en");

Config Method (OIDC Class)

Sets or retrieves a configuration setting.

Syntax

public String config(String configurationString);

Remarks

Config is a generic method available in every class. It is used to set and retrieve configuration settings for the class.

These settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the class, access to these internal properties is provided through the Config method.

To set a configuration setting named PROPERTY, you must call Config("PROPERTY=VALUE"), where VALUE is the value of the setting expressed as a string. For boolean values, use the strings "True", "False", "0", "1", "Yes", or "No" (case does not matter).

To read (query) the value of a configuration setting, you must call Config("PROPERTY"). The value will be returned as a string.

DoEvents Method (OIDC Class)

This method processes events from the internal message queue.

Syntax

public void doEvents();

Remarks

When DoEvents is called, the class processes any available events. If no events are available, it waits for a preset period of time, and then returns.

GetAuthorizationURL Method (OIDC Class)

Builds the URL for an OpenID provider's authorization server.

Syntax

public String getAuthorizationURL();

Remarks

This method will build the authorization URL that should be used to direct the user to the OpenID providers authorization server. Before calling this method, the class will need to be configured so that it has the needed information. The discovery document for the OpenID provider is used to provide the necessary information about the authorization server like the AuthorizationURL. If needed, the ServerAuthURL configuration setting can be used to override or manually provide the URL of the authorization server. The rest of the information needed can be provided through the following properties or configuration setting.

• AuthorizationScope (Required)
• ClientId (Required)
• GrantType (Required)
• ReturnURL (Required)
• UsePKCE (Optional)
• Display (Optional)
• IDTokenHint (Optional)
• LoginHint (Optional)
• Prompt (Optional)
• ResponseType (Optional)

GetDiscoveryMetadata Method (OIDC Class)

Get a specific metadata value from the discovery document.

Syntax

public String getDiscoveryMetadata(String metadataName);

Remarks

This method will search the current discovery document for a specific metadata value. This can take the metadata name or the JSON path. This works on documents that have been provided by both the LoadDiscoveryDoc and RequestDiscoveryDoc methods. For example, to get the authorization endpoint metadata field from the document both examples are valid:

Metadata Name oidc.GetDiscoveryMetadata("authorization_endpoint");

JSON Path oidc.GetDiscoveryMetadata("/json/authorization_endpoint");

GetIdTokenClaim Method (OIDC Class)

Get a specific claim from the ID Token.

Syntax

public String getIdTokenClaim(String claimName);

Remarks

This method will search the current ID Token for a specific claim. This can take the claim name (defined by the specification) or a JSON path. For example, to get the audience claim from the ID Token both examples are valid:

Claim Name oidc.GetIdTokenClaim("aud");

JSON Path oidc.GetIdTokenClaim("/json/aud");

GetQueryParam Method (OIDC Class)

Get a specific claim from the current HTTP request.

Syntax

public String getQueryParam(String paramName);

Remarks

Searches the current context (after process or parse is called) or the HTTPRequestHeaders property for a specific query parameter and returns the value. For example, if the request that was recently processed by the class contains the state parameter, then the following code would return the value of the state returned from the authorization server.

oidc.ProcessHTTPRequest(); string state = oidc.GetQueryParam("state");

GetUserInfoClaim Method (OIDC Class)

Get a specific claim from the UserInfo response.

Syntax

public String getUserInfoClaim(String claimName);

Remarks

This method will search the most recent response from the RequestUserInfo method response for a specific claim. This can take the claim name (defined by the specification) or a JSON path. For example, to get the audience claim from the response both examples are valid:

Claim Name oidc.GetUserInfoClaim("aud");

JSON Path oidc.GetUserInfoClaim("/json/aud");

Interrupt Method (OIDC Class)

This method interrupts the current method.

Syntax

public void interrupt();

Remarks

If there is no method in progress, Interrupt simply returns, doing nothing.

LoadDiscoveryDoc Method (OIDC Class)

Loads in a raw discovery document.

Syntax

public void loadDiscoveryDoc(String documentData);

Remarks

Loads a discovery document directly from documentData parameter. Typically, this can be used to reload a discovery document that has been previously retrieved by the RequestDiscoveryDoc method.

LoadSignerJWKS Method (OIDC Class)

Loads in the signer JWKS directly from a raw JWKS blob.

Syntax

public void loadSignerJWKS(String jwksData);

Remarks

Loads the JSON Web Keys Set (JWKS) provided through the jwksData parameter. Calling this method will set the SignerJWKS property and SignerCerts collection without making a request to the SignerCertURL endpoint. Typically, this will be used to reload a JWKS that we previously requested by the RequestSignerCerts method.

ParseHTTPRequest Method (OIDC Class)

Parse the current HTTP request without additional processing.

Syntax

public void parseHTTPRequest(Object request);

Remarks

Parses the current HTTP request and if applicable parses the ID Token, authorization code, or error information out from it. Unlike the ProcessHTTPRequest method, this method will not do any additional processing. Typically, this method is used with others like RequestSignerCerts ValidateIdToken, and RequestTokens.

The HTTP Request is taken directly from the HTTPRequestHeaders and HTTPRequest properties if set, otherwise it will try to read the HTTP context. If the method is able to parse the HTTP request and headers, it will also set the HTTPRequestHeaders and HTTPRequest properties.

ProcessHTTPRequest Method (OIDC Class)

Process the current HTTP request.

Syntax

public void processHTTPRequest(Object request);

Remarks

. Parses the current HTTP request and processes the results. Depending on the GrantType and ResponseType settings when the request was created, the processing flow will change. Generally, the method is the equivalent to calling the following methods.

• ParseHTTPRequest
• RequestTokens
• RequestSignerCerts (if SignerCerts is not set)
• ValidateIdToken

RequestDiscoveryDoc Method (OIDC Class)

Requests the OpenID Discovery Document.

Syntax

public void requestDiscoveryDoc(String URL);

Remarks

This method gets the OpenID Connect Discovery Document specified by the URL parameter and parses the response. The discover document contains details about the OpenID Provider configuration including endpoint URLs, supported claims and response types, and more.

The discovery document URL is typically published by an OpenID Provider (OP) and must be known before calling this method. The format of the URL is standardized and typically takes the form:

https://www.youropenidserver.com/.well-known/openid-configuration

Call RequestDiscoveryDoc before calling GetAuthorizationURL to populate the class properties with information required to request authorization. The retrieved information includes endpoint URLs as well as the OpenID public certificates used to verify the signature on the ID Token. After calling this method the DiscoveryDocDetails property is populated. The Content field may be stored, and reloaded using the LoadDiscoveryDoc method, to avoid calling RequestDiscoveryDoc on subsequent authorization requests.

To access values not automatically parsed by the class the GetDiscoveryMetadata method can be used to query for a specific metadata entry.

RequestSignerCerts Method (OIDC Class)

Requests the signing certificates from the OpenID provider.

Syntax

public void requestSignerCerts();

Remarks

Makes the request to the SignerCertURL to get the current signer certificates for the OpenID provider. The OpenID provider will return a JSON Web Key Set (JWKS) that represents the set of signing certificates that might be used when signing ID Tokens. The class will automatically populate the SignerCerts collection with the signer certificates parsed from the JWKS. Additionally, this method will the set the SignerJWKS property with the returned JWKS. The SignerJWKS property can be saved for later and be used with the LoadSignerJWKS method to avoid needed to use this method for subsequent requests.

RequestTokens Method (OIDC Class)

Requests new tokens from the token server.

Syntax

public void requestTokens();

Remarks

Makes a request to the token server to exchange an AuthorizationCode or RefreshToken for a set of tokens. The specific tokens returned depends on the grant type and OpenID provider but can be a combination of an AccessToken, ID Token (IdTokenInfo), and RefreshToken.

If an ID Token is returned, then the class will automatically attempt to verify it using the values specified by the DiscoveryDocDetails, ClientId, and SignerCerts properties. See ValidateIdToken for more information.

The class will make the request to the TokenURL field or the ServerTokenURL configuration setting if it has been set.

RequestUserInfo Method (OIDC Class)

Request the information of a user.

Syntax

public void requestUserInfo();

Remarks

Makes a request to get a specific users info based on the current AccessToken. The request is made to the UserInfo endpoint which is defined by the UserInfoURL field when parsed from a discovery doc. The URL can also be provided directly to the class by setting the ServerUserInfoURL configuration setting.

When a valid response is returned from the UserInfo endpoint, the class will populate the fields in the UserDetails property. For uncommon or custom claims, the GetUserInfoClaim method can be used to get claims not covered by the UserDetails property.

Reset Method (OIDC Class)

This method will reset the class.

Syntax

public void reset();

Remarks

This method will reset the class's properties to their default values.

ValidateIdToken Method (OIDC Class)

Validate an ID Token.

Syntax

public void validateIdToken();

Remarks

Validates and parses the current ID Token.

Validation

For validation, the method will first check the signature of the ID Token using the SignerCerts collection which contains the public certificates of the certificates used to sign the original ID Token. If the SignerCerts collection is not populated, then a request will be made to the SignerCertURL field or the ServerSignerCertURL configuration setting if set. This is the equivalent to calling the RequestSignerCerts method.

Then, the class will verify that the Issuer field matches what is expected in the Issuer field. Next the Audience will be checked to ensure that it matches the ClientId property. The ExpectedIssuer and ExpectedAudience configuration settings can be used to override the typical expected values. The last check is to ensure that the IssuedTime and ExpTime are valid based on the current time. Additionally, if the nbf (Not Before) claim is present, that will also be verified.

If verification fails, the class will throw an exception with the matching error code. If certain steps in the verification process should be skipped, the IdTokenVerificationFlags configuration setting can be used.

Parsing

Once verified, the class will parse the ID Token and populate the IdTokenInfo and UserDetails properties. Any uncommon or custom claims can be retrieve by calling the GetIdTokenClaim method.

Getting/loading an ID Token The ID Token can be populated directly by setting the IdTokenContent field or by calling the ParseHTTPRequest, ProcessHTTPRequest, or RequestTokens methods. Typically, the component will automatically validate and parse an ID Token if it is found. The exception is if the ParseHTTPRequest method is called which will only set the IdTokenContent field.

Connected Event (OIDC Class)

This event is fired immediately after a connection completes (or fails).

Syntax

public class DefaultOIDCEventListener implements OIDCEventListener {
  ...
  public void connected(OIDCConnectedEvent e) {}
  ...
}

public class OIDCConnectedEvent {
  public int statusCode;
  public String description;
}

Remarks

If the connection is made normally, StatusCode is 0 and Description is "OK".

If the connection fails, StatusCode has the error code returned by the Transmission Control Protocol (TCP)/IP stack. Description contains a description of this code. The value of StatusCode is equal to the value of the error.

Please refer to the Error Codes section for more information.

ConnectionStatus Event (OIDC Class)

This event is fired to indicate changes in the connection state.

Syntax

public class DefaultOIDCEventListener implements OIDCEventListener {
  ...
  public void connectionStatus(OIDCConnectionStatusEvent e) {}
  ...
}

public class OIDCConnectionStatusEvent {
  public String connectionEvent;
  public int statusCode;
  public String description;
}

Remarks

The ConnectionStatus event is fired when the connection state changes: for example, completion of a firewall or proxy connection or completion of a security handshake.

The ConnectionEvent parameter indicates the type of connection event. Values may include the following:

Disconnected Event (OIDC Class)

This event is fired when a connection is closed.

Syntax

public class DefaultOIDCEventListener implements OIDCEventListener {
  ...
  public void disconnected(OIDCDisconnectedEvent e) {}
  ...
}

public class OIDCDisconnectedEvent {
  public int statusCode;
  public String description;
}

Remarks

If the connection is broken normally, StatusCode is 0 and Description is "OK".

If the connection is broken for any other reason, StatusCode has the error code returned by the Transmission Control Protocol (TCP/IP) subsystem. Description contains a description of this code. The value of StatusCode is equal to the value of the TCP/IP error.

Please refer to the Error Codes section for more information.

EndTransfer Event (OIDC Class)

This event is fired when a document finishes transferring.

Syntax

public class DefaultOIDCEventListener implements OIDCEventListener {
  ...
  public void endTransfer(OIDCEndTransferEvent e) {}
  ...
}

public class OIDCEndTransferEvent {
  public int direction;
}

Remarks

The EndTransfer event is fired first when the client finishes sending data to the server (in a POST or PUT request) and then when the document text finishes transferring from the server to the local host.

The Direction parameter shows whether the client (0) or the server (1) is sending the data.

Error Event (OIDC Class)

Fired when information is available about errors during data delivery.

Syntax

public class DefaultOIDCEventListener implements OIDCEventListener {
  ...
  public void error(OIDCErrorEvent e) {}
  ...
}

public class OIDCErrorEvent {
  public int errorCode;
  public String description;
}

Remarks

The Error event is fired in case of exceptional conditions during message processing. Normally the class throws an exception.

The ErrorCode parameter contains an error code, and the Description parameter contains a textual description of the error. For a list of valid error codes and their descriptions, please refer to the Error Codes section.

Header Event (OIDC Class)

This event is fired every time a header line comes in.

Syntax

public class DefaultOIDCEventListener implements OIDCEventListener {
  ...
  public void header(OIDCHeaderEvent e) {}
  ...
}

public class OIDCHeaderEvent {
  public String field;
  public String value;
}

Remarks

The Field parameter contains the name of the HTTP header (which is the same as it is delivered). The Value parameter contains the header contents.

If the header line being retrieved is a continuation header line, then the Field parameter contains "" (empty string).

Log Event (OIDC Class)

This event fires once for each log message.

Syntax

public class DefaultOIDCEventListener implements OIDCEventListener {
  ...
  public void log(OIDCLogEvent e) {}
  ...
}

public class OIDCLogEvent {
  public int logLevel;
  public String message;
  public String logType;
}

Remarks

This event fires once for each log message generated by the class. The verbosity is controlled by the LogLevel setting.

LogLevel indicates the level of message. Possible values are as follows:

The value 1 (Info) logs basic information, including the URL, HTTP version, and status details.

The value 2 (Verbose) logs additional information about the request and response.

The value 3 (Debug) logs the headers and body for both the request and response, as well as additional debug information (if any).

Message is the log entry.

LogType identifies the type of log entry. Possible values are as follows:

• "Info"
• "RequestHeaders"
• "ResponseHeaders"
• "RequestBody"
• "ResponseBody"
• "ProxyRequest"
• "ProxyResponse"
• "FirewallRequest"
• "FirewallResponse"

Redirect Event (OIDC Class)

This event is fired when a redirection is received from the server.

Syntax

public class DefaultOIDCEventListener implements OIDCEventListener {
  ...
  public void redirect(OIDCRedirectEvent e) {}
  ...
}

public class OIDCRedirectEvent {
  public String location;
  public boolean accept; //read-write
}

Remarks

This event is fired in cases in which the client can decide whether or not to continue with the redirection process. The Accept parameter is always True by default, but if you do not want to follow the redirection, Accept may be set to False, in which case the class throws an exception. Location is the location to which the client is being redirected. Further control over redirection is provided in the FollowRedirects property.

SetCookie Event (OIDC Class)

This event is fired for every cookie set by the server.

Syntax

public class DefaultOIDCEventListener implements OIDCEventListener {
  ...
  public void setCookie(OIDCSetCookieEvent e) {}
  ...
}

public class OIDCSetCookieEvent {
  public String name;
  public String value;
  public String expires;
  public String domain;
  public String path;
  public boolean secure;
}

Remarks

The SetCookie event is fired for every Set-Cookie: header received from the HTTP server.

The Name parameter contains the name of the cookie, with the corresponding value supplied in the Value parameter.

The Expires parameter contains an expiration time for the cookie (if provided by the server). The time format used is "Weekday, DD-Mon-YY HH:MM:SS GMT". If the server does not provide an expiration time, the Expires parameter will be an empty string. In this case, the convention is to drop the cookie at the end of the session.

The Domain parameter contains a domain name to limit the cookie to (if provided by the server). If the server does not provide a domain name, the Domain parameter will be an empty string. The convention in this case is to use the server specified in the URL (URLServer) as the cookie domain.

The Path parameter contains a path name to limit the cookie to (if provided by the server). If the server does not provide a cookie path, the Path parameter will be an empty string. The convention in this case is to use the path specified in the URL (URLPath) as the cookie path.

The Secure parameter specifies whether the cookie is secure. If the value of this parameter is True, the cookie value must be submitted only through a secure (HTTPS) connection.

SSLServerAuthentication Event (OIDC Class)

Fired after the server presents its certificate to the client.

Syntax

public class DefaultOIDCEventListener implements OIDCEventListener {
  ...
  public void SSLServerAuthentication(OIDCSSLServerAuthenticationEvent e) {}
  ...
}

public class OIDCSSLServerAuthenticationEvent {
  public byte[] certEncoded;
  public String certSubject;
  public String certIssuer;
  public String status;
  public boolean accept; //read-write
}

Remarks

During this event, the client can decide whether or not to continue with the connection process. The Accept parameter is a recommendation on whether to continue or close the connection. This is just a suggestion: application software must use its own logic to determine whether or not to continue.

When Accept is False, Status shows why the verification failed (otherwise, Status contains the string OK). If it is decided to continue, you can override and accept the certificate by setting the Accept parameter to True.

SSLStatus Event (OIDC Class)

Fired when secure connection progress messages are available.

Syntax

public class DefaultOIDCEventListener implements OIDCEventListener {
  ...
  public void SSLStatus(OIDCSSLStatusEvent e) {}
  ...
}

public class OIDCSSLStatusEvent {
  public String message;
}

Remarks

The event is fired for informational and logging purposes only. This event tracks the progress of the connection.

StartTransfer Event (OIDC Class)

This event is fired when a document starts transferring (after the headers).

Syntax

public class DefaultOIDCEventListener implements OIDCEventListener {
  ...
  public void startTransfer(OIDCStartTransferEvent e) {}
  ...
}

public class OIDCStartTransferEvent {
  public int direction;
}

Remarks

The StartTransfer event is fired first when the client starts sending data to the server (in a POST or PUT request) and then when the document text starts transferring from the server to the local host.

The Direction parameter shows whether the client (0) or the server (1) is sending the data.

Status Event (OIDC Class)

This event is fired when the HTTP status line is received from the server.

Syntax

public class DefaultOIDCEventListener implements OIDCEventListener {
  ...
  public void status(OIDCStatusEvent e) {}
  ...
}

public class OIDCStatusEvent {
  public String HTTPVersion;
  public int statusCode;
  public String description;
}

Remarks

HTTPVersion is a string containing the HTTP version string as returned from the server (e.g., "1.1").

StatusCode contains the HTTP status code (e.g., 200), and Description the associated message returned by the server (e.g., "OK").

Transfer Event (OIDC Class)

This event is fired while a document transfers (delivers document).

Syntax

public class DefaultOIDCEventListener implements OIDCEventListener {
  ...
  public void transfer(OIDCTransferEvent e) {}
  ...
}

public class OIDCTransferEvent {
  public int direction;
  public long bytesTransferred;
  public int percentDone;
  public byte[] text;
}

Remarks

The Text parameter contains the portion of the document text being received. It is empty if data are being posted to the server.

The BytesTransferred parameter contains the number of bytes transferred in this Direction since the beginning of the document text (excluding HTTP response headers).

The Direction parameter shows whether the client (0) or the server (1) is sending the data.

The PercentDone parameter shows the progress of the transfer in the corresponding direction. If PercentDone can not be calculated the value will be -1.

Note: Events are not re-entrant. Performing time-consuming operations within this event will prevent it from firing again in a timely manner and may affect overall performance.

Certificate Type

This is the digital certificate being used.

Remarks

This type describes the current digital certificate. The certificate may be a public or private key. The fields are used to identify or select certificates.

Fields

Constructors

public Certificate();

public Certificate( certificateFile);

public Certificate( encoded);

public Certificate( storeType,  store,  storePassword,  subject);

public Certificate( storeType,  store,  storePassword,  subject,  configurationString);

public Certificate( storeType,  store,  storePassword,  encoded);

public Certificate( storeType,  store,  storePassword,  subject);

public Certificate( storeType,  store,  storePassword,  subject,  configurationString);

public Certificate( storeType,  store,  storePassword,  encoded);

DiscoveryDocDetails Type

Details about the OpenID provider's discovery document.

Remarks

The fields of this type correspond to metadata details from an OpenID provider's discovery document.

Fields

Constructors

public DiscoveryDocDetails();

Firewall Type

The firewall the class will connect through.

Remarks

When connecting through a firewall, this type is used to specify different properties of the firewall, such as the firewall Host and the FirewallType.

Fields

Constructors

public Firewall();

HTTPCookie Type

An HTTP cookie can be either sent to or received from the server.

Remarks

An HTTP cookie can store the cookies that are to be sent to the server. It also may store the cookies sent by the server.

Cookies that are to be sent to the server must have the Name and Value fields supplied before submitting the URL. When the SetCookie event is fired, however, all of the fields of an HTTPCookie are filled out accordingly.

Fields

Constructors

public HTTPCookie();

public HTTPCookie( name,  value);

IdTokenInfo Type

This type holds details about an ID Token.

Remarks

The fields of this type correspond to claims from the ID Token.

Fields

Constructors

public IdTokenInfo();

OAuthParam Type

This is the parameter to be used in the request or received in the response.

Remarks

This type describes a parameter that is used in a request or received in the response.

Fields

Constructors

public OAuthParam();

public OAuthParam( name,  value);

Proxy Type

The proxy the class will connect to.

Remarks

When connecting through a proxy, this type is used to specify different properties of the proxy, such as the Server and the AuthScheme.

Fields

Constructors

public Proxy();

public Proxy( server,  port);

public Proxy( server,  port,  user,  password);

UserDetails Type

This type holds details about the user.

Remarks

The fields of this type correspond to claims about the user.

Fields

Constructors

public UserDetails();

Config Settings (OIDC Class)

OIDC Config Settings

HTTP Config Settings

TCPClient Config Settings

SSL Config Settings

-----BEGIN CERTIFICATE-----
MIIEKzCCAxOgAwIBAgIRANTET4LIkxdH6P+CFIiHvTowDQYJKoZIhvcNAQELBQAw
... Intermediate Cert ...
eWHV5OW1K53o/atv59sOiW5K3crjFhsBOd5Q+cJJnU+SWinPKtANXMht+EDvYY2w
F0I1XhM+pKj7FjDr+XNj
-----END CERTIFICATE-----
\r \n
-----BEGIN CERTIFICATE-----
MIIEFjCCAv6gAwIBAgIQetu1SMxpnENAnnOz1P+PtTANBgkqhkiG9w0BAQUFADBp
... Root Cert ...
d8q23djXZbVYiIfE9ebr4g3152BlVCHZ2GyPdjhIuLeH21VbT/dyEHHA
-----END CERTIFICATE-----

-----BEGIN CERTIFICATE-----
MIIEKzCCAxOgAwIBAgIRANTET4LIkxdH6P+CFIiHvTowDQYJKoZIhvcNAQELBQAw
... Intermediate Cert ...
eWHV5OW1K53o/atv59sOiW5K3crjFhsBOd5Q+cJJnU+SWinPKtANXMht+EDvYY2w
F0I1XhM+pKj7FjDr+XNj
-----END CERTIFICATE-----
\r \n
-----BEGIN CERTIFICATE-----
MIIEFjCCAv6gAwIBAgIQetu1SMxpnENAnnOz1P+PtTANBgkqhkiG9w0BAQUFADBp
... Root Cert ...
d8q23djXZbVYiIfE9ebr4g3152BlVCHZ2GyPdjhIuLeH21VbT/dyEHHA
-----END CERTIFICATE-----

-----BEGIN CERTIFICATE-----
MIIEKzCCAxOgAwIBAgIRANTET4LIkxdH6P+CFIiHvTowDQYJKoZIhvcNAQELBQAw
... Intermediate Cert...
eWHV5OW1K53o/atv59sOiW5K3crjFhsBOd5Q+cJJnU+SWinPKtANXMht+EDvYY2w
F0I1XhM+pKj7FjDr+XNj
-----END CERTIFICATE-----
\r \n
-----BEGIN CERTIFICATE-----
MIIEFjCCAv6gAwIBAgIQetu1SMxpnENAnnOz1P+PtTANBgkqhkiG9w0BAQUFADBp
... Root Cert...
d8q23djXZbVYiIfE9ebr4g3152BlVCHZ2GyPdjhIuLeH21VbT/dyEHHA
-----END CERTIFICATE-----

Socket Config Settings

Base Config Settings

Trappable Errors (OIDC Class)

OpenID Errors

HTTP Errors

TCPClient Errors

SSL Errors

TCP/IP Errors