OIDC Component

Properties   Methods   Events   Config Settings   Errors  

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

Syntax

TciOIDC

Remarks

The OIDC component provides a simple way to authenticate users to your web application using OpenID Connect, making it easy to add SSO support to web applications. Through OpenID Connect, the 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 sensitive user 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 to which users will be returned 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. The OIDC standard 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, 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 component 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 properties 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 property 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 (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 property which is automatically parsed to fill the SignerCerts properties. If the SignerCerts properties is empty and the component needs to verify the ID Token, the component 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 again. This allows the Relying Party to cache the SignerJWKS property and reuse it later, reducing 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 redirected 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 obtained 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 component 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 to which the user should be directed 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 ParseOIDCResponse and ProcessOIDCResponse methods are used to handle HTTP requests that contain an OIDC response from an OpenID Provider. Generally, unless additional considerations or control are needed, the ProcessOIDCResponse method should be used. ProcessOIDCResponse will parse the incoming response from the OpenID Provider 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 request to the token server and handle/validate the response.

The ParseOIDCResponse 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 component provides the ParseOIDCResponse and ProcessOIDCResponse methods to make it simple to get the required information from a redirect.

If the current HTTP context is unavailable, for instance when the component is not used directly within a web application, the HTTP headers and body that contain the OIDC response can be supplied by setting the OIDCResponseHeaders and OIDCResponseBody properties. Additionally, if working within a framework that makes it difficult to get the raw HTTP headers and body, the AuthorizationCode configuration setting can also be set to provide the authorization code directory to the component.

The rest of the examples in this section will assume that the ParseOIDCResponse method is being used to better break down each step that is done by the component. See the ProcessOIDCResponse 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 and the RefreshToken will be used instead.

Usage: Request Tokens

The RequestTokens method is used in the following example to make a request to the token server after ParseOIDCResponse has been called. //Parse OIDC Response oidc.ParseOIDCResponse(); //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 component receives an ID Token after calling ParseOIDCResponse, ProcessOIDCResponse, 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 and Parse an ID Token

In a case where an ID Token is provided directly to the component, the ValidateIdToken method can be used to validate it, and the ParseIdToken method can be used to parse it. The following example will set up the component with the information needed to validate and parse 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. } //Parse the validated ID Token. oidc.ParseIdToken(); string issuer = oidc.IdTokenInfo.Issuer;

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 component will set the properties in the UserDetails property with the corresponding information. If there is a claim that is not found in the UserDetails property, 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 component 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 component with short descriptions. Click on the links for further details.

Method List

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

Event List

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

Config Settings

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

AccessToken Property (OIDC Component)

The access token received from an OpenID provider.

Syntax

property AccessToken: String read get_AccessToken write set_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 set to ogtAuthorizationCode by default. When ResponseType contains code (ogtAuthorizationCode and ogtHybrid), the AccessToken is provided by the TokenURL. When ResponseType contains token (ogtAuthorizationCode and ogtHybrid), the AccessToken is provided by the AuthorizationURL.

AuthorizationScope Property (OIDC Component)

The authorization scope used during authorization.

Syntax

property AuthorizationScope: String read get_AuthorizationScope write set_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 must always be present. The default value is openid.

After calling ProcessOIDCResponse or ParseOIDCResponse, 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 Component)

The error code from a recently parsed OIDC response.

Syntax

property AuthzResponseCode: String read get_AuthzResponseCode;

Default Value

''

Remarks

This property holds the most recent error response code from an OIDC response if found. This is set when ParseOIDCResponse or ProcessOIDCResponse is called 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 response provided a URL to a page that describes the error.

This property is read-only.

AuthzResponseDesc Property (OIDC Component)

The error description from a recently parsed OIDC response.

Syntax

property AuthzResponseDesc: String read get_AuthzResponseDesc;

Default Value

''

Remarks

This property holds the most recent error response description from an OIDC response if found. This is set when ParseOIDCResponse or ProcessOIDCResponse is called 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 Component)

The Id of the client assigned when registering the application.

Syntax

property ClientId: String read get_ClientId write set_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 ProcessOIDCResponse and RequestTokens. Additionally, it is used to verify the Audiences property of an ID Token when calling the ValidateIdToken, ProcessOIDCResponse, and possibly RequestTokens methods.

ClientSecret Property (OIDC Component)

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

Syntax

property ClientSecret: String read get_ClientSecret write set_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 ProcessOIDCResponse.

DiscoveryDocDetails Property (OIDC Component)

Details about the OpenID provider's discovery document.

Syntax

property DiscoveryDocDetails: TciDiscoveryDocDetails read get_DiscoveryDocDetails;

Remarks

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 Component)

A set of properties related to firewall access.

Syntax

property Firewall: TciFirewall read get_Firewall write set_Firewall;

Remarks

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

FollowRedirects Property (OIDC Component)

Determines what happens when the server issues a redirect.

Syntax

property FollowRedirects: TciTFollowRedirects read get_FollowRedirects write set_FollowRedirects;

TciTFollowRedirects = (
  frNever,
  frAlways,
  frSameScheme
);

Default Value

frNever

Remarks

This property determines what happens when the server issues a redirect. Normally, the component 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 component raises 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 component raises an exception instead.

GrantType Property (OIDC Component)

The grant type defining the authentication flow.

Syntax

property GrantType: TciTGrantTypes read get_GrantType write set_GrantType;

TciTGrantTypes = (
  ogtAuthorizationCode,
  ogtImplicit,
  ogtHybrid
);

Default Value

ogtAuthorizationCode

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 component using the ParseOIDCResponse and ProcessOIDCResponse 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 ProcessOIDCResponse or calling the RequestTokens method after parsing, the component will make a request to the token server and return the 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 ProcessOIDCResponse or calling the RequestTokens method after parsing, the component will make a request to the token server and set the AccessToken property and the IdTokenInfo property if provided again. 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.

IdTokenInfo Property (OIDC Component)

Information about the current ID Token.

Syntax

property IdTokenInfo: TciIdTokenInfo read get_IdTokenInfo;

Remarks

This property holds details about the ID Token.

When an ID Token is parsed either by calling ParseIdToken or retrieved after calling ProcessOIDCResponse 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.

OIDCResponseBody Property (OIDC Component)

The HTTP body of an OIDC response.

Syntax

property OIDCResponseBody: String read get_OIDCResponseBody write set_OIDCResponseBody;

Default Value

''

Remarks

This property specifies the HTTP body for an OIDC response. This can be set to directly provide the HTTP body of the OIDC response to be processed by the ParseOIDCResponse or ProcessOIDCResponse methods. This property is also populated with the HTTP body that is parsed from the HTTP context if used by the ParseOIDCResponse or ProcessOIDCResponse methods.

OIDCResponseHeaders Property (OIDC Component)

The HTTP headers of an OIDC response.

Syntax

property OIDCResponseHeaders: String read get_OIDCResponseHeaders write set_OIDCResponseHeaders;

Default Value

''

Remarks

This property specifies the HTTP headers for an OIDC response. This can be set to directly provide the HTTP headers of the OIDC response to be processed by the ParseOIDCResponse or ProcessOIDCResponse methods. This property is also populated with the HTTP headers that are parsed from the HTTP context if used by the ParseOIDCResponse or ProcessOIDCResponse methods.

OtherHeaders Property (OIDC Component)

Other headers as determined by the user (optional).

Syntax

property OtherHeaders: String read get_OtherHeaders write set_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 ('#13#10') .

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 component beyond what is provided.

This property is not available at design time.

Params Property (OIDC Component)

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

Syntax

property Params: TciOAuthParamList read get_Params write set_Params;

Remarks

This property 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 Component)

A set of properties related to proxy access.

Syntax

property Proxy: TciProxy read get_Proxy write set_Proxy;

Remarks

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

RefreshToken Property (OIDC Component)

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

Syntax

property RefreshToken: String read get_RefreshToken write set_RefreshToken;

Default Value

''

Remarks

This property is set by the component when it receives a refresh token after the ProcessOIDCResponse or RequestTokens methods make 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 component use a RefreshToken, first the application will need to save the refresh token in a secure location. Refresh tokens 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 Component)

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

Syntax

property ReturnURL: String read get_ReturnURL write set_ReturnURL;

Default Value

''

Remarks

This property specifies 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 containing OIDC responses using the ProcessOIDCResponse or ParseOIDCResponse methods.

SignerCerts Property (OIDC Component)

The signing certificates from an OpenID provider.

Syntax

property SignerCerts: TciCertificateList read get_SignerCerts;

Remarks

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

The properties can be automatically populated when needed if it is empty and a SignerCertURL is available. This can happen when calling ParseOIDCResponse or ProcessOIDCResponse if the response type includes id_token, when calling RequestTokens or ProcessOIDCResponse 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 Component)

The JSON Web Key Set provided by an OpenID provider.

Syntax

property SignerJWKS: String read get_SignerJWKS;

Default Value

''

Remarks

This property holds 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 component makes a request to populate the SignerCerts properties. The RequestSignerCerts method can be used to manually make a request to the SignerCertURL; otherwise, the component will automatically make the request if the properties 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 requests to the SignerCertURL server.

This property is read-only.

SSLAcceptServerCert Property (OIDC Component)

Instructs the component to unconditionally accept the server certificate that matches the supplied certificate.

Syntax

property SSLAcceptServerCert: TciCertificate read get_SSLAcceptServerCert write set_SSLAcceptServerCert;

Remarks

If it finds any issues with the certificate presented by the server, the component 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 Component)

The certificate to be used during Secure Sockets Layer (SSL) negotiation.

Syntax

property SSLCert: TciCertificate read get_SSLCert write set_SSLCert;

Remarks

This property includes the digital certificate that the component 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 Component)

The Secure Sockets Layer/Transport Layer Security (SSL/TLS) implementation to use.

Syntax

property SSLProvider: TciTSSLProviders read get_SSLProvider write set_SSLProvider;

TciTSSLProviders = (
  sslpAutomatic,
  sslpPlatform,
  sslpInternal
);

Default Value

sslpAutomatic

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 component 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 component will select a provider depending on the current platform.

When Automatic is selected, on Windows, the component will use the platform implementation. On Linux/macOS, the component will use the internal implementation. When TLS 1.3 is enabled via SSLEnabledProtocols, the internal implementation is used on all platforms.

SSLServerCert Property (OIDC Component)

The server certificate for the last established connection.

Syntax

property SSLServerCert: TciCertificate read get_SSLServerCert;

Remarks

This property 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 Component)

An opaque value used to maintain state between the request and response.

Syntax

property State: String read get_State write set_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 Component)

The timeout for the component.

Syntax

property Timeout: Integer read get_Timeout write set_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 component will wait for the operation to complete before returning control.

The component 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 component raises 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.

UseNonce Property (OIDC Component)

Whether the Nonce parameter is added.

Syntax

property UseNonce: Boolean read get_UseNonce write set_UseNonce;

Default Value

false

Remarks

If this property is set to true, the nonce parameter will be added to the OIDC authorization request when GetAuthorizationURL is called. In OpenID Connect, the nonce parameter is provided during the authorization request. Then, when the OpenID Provider issues an ID Token, they will include the nonce claim with the same value (similar to State).

If the Nonce configuration setting is not set before calling GetAuthorizationURL the component will generate a new one and set the Nonce setting. The same nonce value will need to be supplied to the component before calling the ProcessOIDCResponse or ValidateIdToken methods. When the component validates an ID Token, it will check the Nonce configuration setting if a nonce claim is found. By default, the nonce claim is not required but setting this property to true will require the nonce claim to be present and match the Nonce configuration setting.

UsePKCE Property (OIDC Component)

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

Syntax

property UsePKCE: Boolean read get_UsePKCE write set_UsePKCE;

Default Value

false

Remarks

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

UserDetails Property (OIDC Component)

The claims about the user.

Syntax

property UserDetails: TciUserDetails read get_UserDetails;

Remarks

This property holds details about the user.

When an ID Token is parsed either by calling ParseIdToken or when it is retrieved after calling ProcessOIDCResponse 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.

AddParam Method (OIDC Component)

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

Syntax

procedure AddParam(ParamName: String; ParamValue: String);

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 you to provide language preferences to the authorization server for a more cohesive user experience. For example, the following 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 Component)

Sets or retrieves a configuration setting.

Syntax

function Config(ConfigurationString: String): String;

Remarks

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

These settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the component, 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 Component)

This method processes events from the internal message queue.

Syntax

procedure DoEvents();

Remarks

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

GetAuthorizationURL Method (OIDC Component)

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

Syntax

function GetAuthorizationURL(): String;

Remarks

This method will build the authorization URL that should be used to direct the user to the OpenID provider's authorization server. Before calling this method, the component 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 settings.

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

GetDiscoveryMetadata Method (OIDC Component)

Gets a specific metadata value from the discovery document.

Syntax

function GetDiscoveryMetadata(metadataName: String): String;

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 of the following are valid:

Metadata Name oidc.GetDiscoveryMetadata("authorization_endpoint");

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

GetIdTokenClaim Method (OIDC Component)

Gets a specific claim from the ID Token.

Syntax

function GetIdTokenClaim(claimName: String): String;

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 of the following are valid:

Claim Name oidc.GetIdTokenClaim("aud");

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

GetQueryParam Method (OIDC Component)

Gets a specific claim from the current OIDC response.

Syntax

function GetQueryParam(paramName: String): String;

Remarks

This method searches the current context (after ProcessOIDCResponse or ParseOIDCResponse is called) or the OIDCResponseHeaders property for a specific query parameter and returns the value. For example, if the response that was recently processed by the component contains the state parameter, then the following code would return the value of the state returned from the authorization server.

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

GetUserInfoClaim Method (OIDC Component)

Gets a specific claim from the UserInfo response.

Syntax

function GetUserInfoClaim(claimName: String): String;

Remarks

This method will search the most recent response from the RequestUserInfo method 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 of the following are valid:

Claim Name oidc.GetUserInfoClaim("aud");

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

Interrupt Method (OIDC Component)

This method interrupts the current method.

Syntax

procedure Interrupt();

Remarks

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

LoadDiscoveryDoc Method (OIDC Component)

Loads in a raw discovery document.

Syntax

procedure LoadDiscoveryDoc(documentData: String);

Remarks

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

LoadSignerJWKS Method (OIDC Component)

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

Syntax

procedure LoadSignerJWKS(jwksData: String);

Remarks

This method loads the JSON Web Keys Set (JWKS) provided through the jwksData parameter. Calling this method will set the SignerJWKS property and populate the SignerCerts properties 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.

ParseIdToken Method (OIDC Component)

Parses an ID Token.

Syntax

procedure ParseIdToken();

Remarks

This method parses the current ID Token. If the method is able to successfully parse the ID Token, it will populate the IdTokenInfo and UserDetails properties. Any uncommon or custom claims can be retrieved by calling the GetIdTokenClaim method. The ID Token can be populated directly by setting the IdTokenContent property or by calling the ParseOIDCResponse, ProcessOIDCResponse, or RequestTokens methods. Typically, the component will automatically validate and parse an ID Token if it is found. The exception is if the ParseOIDCResponse method is called which will only set the IdTokenContent property.

See ValidateIdToken for information on validating an ID Token.

ParseOIDCResponse Method (OIDC Component)

Parses the current OIDC response without additional processing.

Syntax

procedure ParseOIDCResponse();

Remarks

This method parses the OIDC response from the current HTTP request and, if applicable, parses the ID Token, authorization code, or error information from it, populating the IdTokenContent, AuthorizationCode, and AuthzResponseCode properties respectively. Unlike the ProcessOIDCResponse method, this method will not do any additional processing. Typically, this method is used with others like RequestSignerCerts, ValidateIdToken, ParseIdToken, and RequestTokens.

The HTTP request is taken directly from the OIDCResponseHeaders and OIDCResponseBody properties if set; otherwise, it will try to read the HTTP context. If this method is able to parse the HTTP request and headers from the HTTP Context, it will also set the OIDCResponseHeaders and OIDCResponseBody properties.

ProcessOIDCResponse Method (OIDC Component)

Processes the current OIDC response.

Syntax

procedure ProcessOIDCResponse();

Remarks

This method parses the OIDC response out of 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, this method is equivalent to calling the following methods:

• ParseOIDCResponse
• RequestTokens
• RequestSignerCerts (if SignerCerts is not set)
• ValidateIdToken
• ParseIdToken

RequestDiscoveryDoc Method (OIDC Component)

Requests the OpenID Discovery Document.

Syntax

procedure RequestDiscoveryDoc(URL: String);

Remarks

This method gets the OpenID Connect Discovery Document specified by the URL parameter and parses the response. The discovery 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 component 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 property 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 component, the GetDiscoveryMetadata method can be used to query for a specific metadata entry.

RequestSignerCerts Method (OIDC Component)

Requests the signing certificates from the OpenID provider.

Syntax

procedure RequestSignerCerts();

Remarks

This method makes a 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 component will automatically populate the SignerCerts properties with the signer certificates parsed from the JWKS. Additionally, this method will set the SignerJWKS property with the returned JWKS. The SignerJWKS property can be saved for later and used with the LoadSignerJWKS method to avoid needing to use this method for subsequent requests.

RequestTokens Method (OIDC Component)

Requests new tokens from the token server.

Syntax

procedure RequestTokens();

Remarks

This method 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 they can be any combination of an AccessToken, ID Token (IdTokenInfo), and RefreshToken.

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

The component will make the request to the TokenURL property or the ServerTokenURL configuration setting if either has been set.

RequestUserInfo Method (OIDC Component)

Requests the information of a user.

Syntax

procedure RequestUserInfo();

Remarks

This method makes a request to get a specific user's info based on the current AccessToken. The request is made to the UserInfo endpoint which is defined by the UserInfoURL property when parsed from a discovery document. The URL can also be provided directly to the component by setting the ServerUserInfoURL configuration setting.

When a valid response is returned from the UserInfo endpoint, the component will populate the properties 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 Component)

This method will reset the component.

Syntax

procedure Reset();

Remarks

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

ValidateIdToken Method (OIDC Component)

Validates an ID Token.

Syntax

procedure ValidateIdToken();

Remarks

This method validates the current ID Token. The ID Token can be populated directly by setting the IdTokenContent property or by calling the ParseOIDCResponse, ProcessOIDCResponse, or RequestTokens methods. Typically, the component will automatically validate and parse an ID Token if it is found. The exception is if the ParseOIDCResponse method is called which will only set the IdTokenContent property.

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

Then, the component will validate that the Issuer property matches what is expected in the Issuer property. Next, the Audiences 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 validation fails, the component will throw an exception with the matching error code. If certain steps in the verification process should be skipped, the IdTokenValidationFlags configuration setting can be used.

Error Event (OIDC Component)

Fired when information is available about errors during data delivery.

Syntax

type TErrorEvent = procedure (
  Sender: TObject;
  ErrorCode: Integer;
  const Description: String
) of Object;

property OnError: TErrorEvent read FOnError write FOnError;

Remarks

The Error event is fired in case of exceptional conditions during message processing. Normally the component raises 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.

Log Event (OIDC Component)

Fired once for each log message.

Syntax

type TLogEvent = procedure (
  Sender: TObject;
  LogLevel: Integer;
  const Message: String;
  const LogType: String
) of Object;

property OnLog: TLogEvent read FOnLog write FOnLog;

Remarks

This event is fired once for each log message generated by the component. 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 Component)

Fired when a redirection is received from the server.

Syntax

type TRedirectEvent = procedure (
  Sender: TObject;
  const Location: String;
  var Accept: Boolean
) of Object;

property OnRedirect: TRedirectEvent read FOnRedirect write FOnRedirect;

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 component raises an exception. Location is the location to which the client is being redirected. Further control over redirection is provided in the FollowRedirects property.

SSLServerAuthentication Event (OIDC Component)

Fired after the server presents its certificate to the client.

Syntax

type TSSLServerAuthenticationEvent = procedure (
  Sender: TObject;
  const CertEncoded: String;
  const CertEncodedB: TBytes;
  const CertSubject: String;
  const CertIssuer: String;
  const Status: String;
  var Accept: Boolean
) of Object;

property OnSSLServerAuthentication: TSSLServerAuthenticationEvent read FOnSSLServerAuthentication write FOnSSLServerAuthentication;

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 Component)

Fired when secure connection progress messages are available.

Syntax

type TSSLStatusEvent = procedure (
  Sender: TObject;
  const Message: String
) of Object;

property OnSSLStatus: TSSLStatusEvent read FOnSSLStatus write FOnSSLStatus;

Remarks

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

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

>

constructor Create();

constructor Create(valEncoded: TBytes);

constructor Create(valStoreType: TciCertStoreTypes; valStore: String; valStorePassword: String; valSubject: String);

constructor Create(valStoreType: TciCertStoreTypes; valStore: TBytes; valStorePassword: String; valSubject: String);

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

constructor Create();

Firewall Type

The firewall the component 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

constructor Create();

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

constructor Create();

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

constructor Create();

constructor Create(valName: String; valValue: String);

Proxy Type

The proxy the component 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

constructor Create();

constructor Create(valServer: String; valPort: Integer);

constructor Create(valServer: String; valPort: Integer; valUser: String; valPassword: String);

UserDetails Type

This type holds details about the user.

Remarks

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

Fields

Constructors

constructor Create();

Config Settings (OIDC Component)

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 Component)

OIDC Errors

The component may also return one of the following error codes, which are inherited from other components.