Endpoints and base URL
NOTE: The providers and endpoints supplied with the interface are fixed and cannot be configured.
The SCIM 2.0 interface can be found in the API Server installation directory under the fixed subdirectory /ApiServer/scim/v2. The base URL is formed as follows:
<http | https>://[<subdomain | server name>.]<domain name>/ApiServer/scim/v2
There are other fixed endpoints. The endpoints are called without any further URL parameters.
-
/ServiceProviderConfig
The endpoint provides information about the options implemented in the service provider, such as the authentication types on offer. The endpoint can be accessed without authentication.
-
/Schemas
The return structure of the endpoint defines all data objects and their properties supported by the provider.
SCIM plugin features
The return structure of the /ServiceproviderConfig endpoint defines, among other things, the features that are supported by the SCIM plugin.
-
patch: When changes are transferred, only individual operations on properties are transferred, not the whole of the object to change.
-
filter: This supports filtering of objects immediately on request or in patch operations.
Authenticating SCIM clients
An authenticationSchemes list is included in the structure returned by the /ServiceproviderConfig endpoint. The list publishes the possible authentication and authorization methods with which the SCIM plugin can be used.
Supported are:
-
HTTP Basic access authentication
-
NTLM Authentication and Kerberos
-
OAuth 2.0 client authorization
Authenticating SCIM plugins in One Identity Manager
To access the One Identity Manager database, the SCIM plugin be authenticated. Authentication is carried out by the One Identity Manager authentication modules. For more information, see the One Identity Manager Authorization and Authentication Guide.
The authentication modules are checked in the following order and the first successful authentication module is used for logging in. Ensure sure that at least one authentication module is enabled and configured. For more information about the authenticating users on the API Server, see the One Identity Manager API Development Guide.
-
Active Directory user account (ADSAccount)
-
HTTP Header (HTTPHeader)
-
OAuth 2.0/OpenID Connect (role-based) (OAuthRoleBased)