Actions related to clients in Aritma ID
- Updates the icon for a custom SSO provider
Aritma ID API (1)
An API for interacting with Aritma ID
Authorization: each endpoint lists the IAM actions the calling subject must be granted in the tenant (also exposed as x-required-actions). Actions are enforced on the static root scope /; a grant on a narrower scope does not satisfy them. When several actions are listed, all are required. Some endpoints only accept user subjects (x-allowed-subject-types); calling them with a client token returns 400 Bad Request.
The properties that defines the behavior of this provider, dependent on which provider that is used, see json schemas for more details
Whether users are automatically provisioned on first login via this provider.
The OAuth 2.0 client ID registered with the identity provider.
The OAuth 2.0 client secret. Leave null for public clients using PKCE.
Whether this provider can be used to verify the user in a higher level of assurance.
The OAuth 2.0 response type to request from the provider.
The claim type used to extract the user's phone number.
The OIDC authority URL of the custom provider.
The OAuth 2.0 scopes to request (space-separated).
Whether to fetch additional claims from the userinfo endpoint after authentication.
- Mock serverhttps://developer.aritma.com/_mock/apis/platform/iam/openapi/iam-openapi/v1/sso/custom
- Payload
- cURL
- C#
- JavaScript
- Python
- Go
- PHP
- Java
- Java 8
{ "scheme": "string", "displayName": "string", "enabled": true, "type": "oidc", "properties": { "loginEnabled": true, "visible": true, "delegationEnabled": false, "autoProvisioningEnabled": true, "clientId": "my-client-id", "clientSecret": "my-client-secret", "verifyEnabled": false, "responseType": "code", "nameClaimType": "name", "emailClaimType": "email", "phoneNumberClaimType": "phone", "subjectClaimType": "sub", "authority": "https://your-idp.example.com", "scope": "openid profile email", "getClaimsFromUserInfoEndpoint": false, "usePkce": false } }
[ { "rel": "self", "href": "/v0/sso/custom/1", "method": "GET" } ]
- Mock serverhttps://developer.aritma.com/_mock/apis/platform/iam/openapi/iam-openapi/v1/sso/custom/{id}/icon
- Payload
- cURL
- C#
- JavaScript
- Python
- Go
- PHP
- Java
- Java 8
- multipart/form-data
- application/json
{
"icon": "string"
}- Mock serverhttps://developer.aritma.com/_mock/apis/platform/iam/openapi/iam-openapi/v1/sso/custom/{id}/icon
- Payload
- cURL
- C#
- JavaScript
- Python
- Go
- PHP
- Java
- Java 8
No request payload- Mock serverhttps://developer.aritma.com/_mock/apis/platform/iam/openapi/iam-openapi/v1/sso/custom/{id}
- Payload
- cURL
- C#
- JavaScript
- Python
- Go
- PHP
- Java
- Java 8
No request payload- Mock serverhttps://developer.aritma.com/_mock/apis/platform/iam/openapi/iam-openapi/v1/sso/custom/{id}
- Payload
- cURL
- C#
- JavaScript
- Python
- Go
- PHP
- Java
- Java 8
No request payloadOK
The unique authentication scheme name used to identify this provider.
The human-readable name shown to users on the login page.
Indicates whether this provider is currently active and available for login.
The provider type name (e.g. Azure, Google, Signicat, Custom).
Provider-specific configuration properties.
Whether users are automatically provisioned on first login via this provider.
The OAuth 2.0 client ID registered with the identity provider.
The OAuth 2.0 client secret. Leave null for public clients using PKCE.
Whether this provider can be used to verify the user in a higher level of assurance.
The OAuth 2.0 response type to request from the provider.
The claim type used to extract the user's phone number.
The OIDC authority URL of the custom provider.
The OAuth 2.0 scopes to request (space-separated).
Whether to fetch additional claims from the userinfo endpoint after authentication.
{ "id": 1, "scheme": "azure-ad", "displayName": "Our Azure AD", "enabled": true, "providerName": "Azure", "type": "oidc", "properties": { "loginEnabled": true, "visible": true, "delegationEnabled": false, "autoProvisioningEnabled": true, "clientId": "my-client-id", "clientSecret": "my-client-secret", "verifyEnabled": false, "responseType": "code", "nameClaimType": "name", "emailClaimType": "email", "phoneNumberClaimType": "phone", "subjectClaimType": "sub", "authority": "https://your-idp.example.com", "scope": "openid profile email", "getClaimsFromUserInfoEndpoint": false, "usePkce": false } }
The properties that defines the behavior of this provider, dependent on which provider that is used, see json schemas for more details
Whether users are automatically provisioned on first login via this provider.
The OAuth 2.0 client ID registered with the identity provider.
The OAuth 2.0 client secret. Leave null for public clients using PKCE.
Whether this provider can be used to verify the user in a higher level of assurance.
The OAuth 2.0 response type to request from the provider.
The claim type used to extract the user's phone number.
The OIDC authority URL of the custom provider.
The OAuth 2.0 scopes to request (space-separated).
Whether to fetch additional claims from the userinfo endpoint after authentication.
- Mock serverhttps://developer.aritma.com/_mock/apis/platform/iam/openapi/iam-openapi/v1/sso/custom/{id}
- Payload
- cURL
- C#
- JavaScript
- Python
- Go
- PHP
- Java
- Java 8
{ "id": 0, "scheme": "string", "displayName": "string", "enabled": true, "type": "oidc", "properties": { "loginEnabled": true, "visible": true, "delegationEnabled": false, "autoProvisioningEnabled": true, "clientId": "my-client-id", "clientSecret": "my-client-secret", "verifyEnabled": false, "responseType": "code", "nameClaimType": "name", "emailClaimType": "email", "phoneNumberClaimType": "phone", "subjectClaimType": "sub", "authority": "https://your-idp.example.com", "scope": "openid profile email", "getClaimsFromUserInfoEndpoint": false, "usePkce": false } }