EndPoints.json
This file acts as the discovery file and tells K2 Business Apps which endpoints are available. A different endpoint can be viewed as a different way of authenticating.
On the login page in K2 Business Apps you can enter a server. Once entered, the file EndPoints.json is retrieved from that server. This file needs to have a certain structure:
{
"EndPoints":
[
{
"Name":
{
"en-US": "Display name in English",
"nl-NL": "Display name in Dutch"
},
"Url": "my endpoint url"
},
{
"Name":
{
"en-US": "Display name in English",
"nl-NL": "Display name in Dutch"
},
"Url": "my second endpoint url",
"IdentityProvider": "my identity provider",
"IsOIDC": true,
"Scopes":
[
"openid",
"offline_access"
],
}
],
"Watermarks":
{
"en-US": "The watermark in English",
"nl-NL": "The watermark in Dutch"
}
}
In the above file you can see several parts:
EndPoints
Name
The display name for this endpoint. It is a mapping of language identifiers to the actual text.
Url
The url K2 Business Apps will use.
IsOIDC (optional)
Whether Open ID Connect is used by this endpoint.
IdentityProvider
If Open ID Connect is used, this identity provider will be used. Indocs provides its own identity provider.
Scopes (optional)
If Open ID Connect is used, you can specify the scopes here.
Watermarks (optional)
This contains the watermark that will be shown in the endpoint field on the login page in K2 Business Apps. It is a mapping of language identifiers to the actual text.