crossTank API, crossTerm API v2 - Authentication
Authentication in Across is based on the commonly used technologies OAuth and OpenID Connect flow. Before continuing with this topic, you might want to get acquainted with them.
- The following resources can be recommended as a basis:
- docs.identityserver.io
- IdentityServer4 QuickStart on GitHub
How to Add a New Client
To be authenticated, it is necessary to validate a client in Across Identity Server (AIS).
To do this on the server on which Across Identity Server is installed (which is usually the Across Core server), edit the file %Across Installation Folder%\Across.IdentityServer\appsettings.json and add the following section:
"Clients": [
{
"ClientId": "CustomWebClient",
"ClientName": "My Custom Web Client",
"AllowedGrantTypes": [ "implicit" ],
"AllowAccessTokensViaBrowser": "true",
"AllowedScopes": [ "openid", "profile", "email", "rights" ],
"RedirectUris": [ "http://localhost:20829/signin-oidc" ]
}
],For more information, see docs.identityserver.io: Client Reference.
There are also several custom fields:
Name | Description | Example |
PlainClientSecrets | Array of secrets. | "PlainClientSecrets": [ "secret1" ] |
DisabledProviders | By default, the following authentication types are available: Across user, Windows user, and Guest. Using this property, you can disable some of these types. | "DisabledProviders": [ "Guest" ] |
Available Grant Types
Value | Description |
password | Resource owner password grant type |
implicit | Implicit grant type |
authorization_code | Authorization code flow |
hybrid | Hybrid flow |
For more information, see docs.identityserver.io: Grant Types.