s Contents

What is UMC Service Layer? 1

Common Response Information 2
Authentication 3
Users 4
Groups 5
Roles 6
UMC APIs Error Codes 7
User Management Component 1.9

UMC Service Layer API

Developer Manual

08/2017
A5E39179405-AC
Guidelines

This manual contains notes of varying importance that should be read with care; i.e.:

Important:

Highlights key information on handling the product, the product itself or to a particular part of the documentation.

Note: Provides supplementary information regarding handling the product, the product itself or a specific part of
the documentation.

Trademarks

All names identified by ® are registered trademarks of Siemens AG.

The remaining trademarks in this publication may be trademarks whose use by third parties for their own purposes
could violate the rights of the owner.

Disclaimer of Liability

We have reviewed the contents of this publication to ensure consistency with the hardware and software
described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the
information in this publication is reviewed regularly and any necessary corrections are included in subsequent
editions.

Security information

Siemens provides products and solutions with industrial security functions that support the secure operation of
plants, systems, machines and networks. In order to protect plants, systems, machines and networks against
cyber threats, it is necessary to implement – and continuously maintain – a holistic, state-of-the-art industrial
security concept. Siemens’ products and solutions only form one element of such a concept.

Customer is responsible to prevent unauthorized access to its plants, systems, machines and networks. Systems,
machines and components should only be connected to the enterprise network or the internet if and to the extent
necessary and with appropriate security measures (e.g. use of firewalls and network segmentation) in place.

Additionally, Siemens’ guidance on appropriate security measures should be taken into account. For more
information about industrial security, please visit http://www.siemens.com/industrialsecurity.

Siemens’ products and solutions undergo continuous development to make them more secure. Siemens strongly
recommends to apply product updates as soon as available and to always use the latest product versions. Use of
product versions that are no longer supported, and failure to apply latest updates may increase customer’s
exposure to cyber threats.

To stay informed about product updates, subscribe to the Siemens Industrial Security RSS Feed under http://www.
siemens.com/industrialsecurity.

Siemens AG A5E39179405-AC Copyright © Siemens AG 2017

Digital Factory 20170808_54746 Technical data subject to change
Postfach 48 48
90026 NÜRNBERG
GERMANY
Contents
1 What is UMC Service Layer? ................................................................................................. 4
2 Common Response Information ........................................................................................... 5
3 Authentication......................................................................................................................... 6
3.1 Login ................................................................................................................................. 6
3.2 Authentication from Claim................................................................................................. 8

4 Users ........................................................................................................................................ 9
4.1 Get All Users..................................................................................................................... 9
4.2 Get User Details............................................................................................................... 11
4.3 Create User..................................................................................................................... 16
4.4 Update User - Basic........................................................................................................ 18
4.5 Update User - Full........................................................................................................... 19
4.6 Unlock User .................................................................................................................... 21
4.7 Delete Users ................................................................................................................... 22
4.8 Browse AD Users............................................................................................................ 23
4.9 Import Users from AD ..................................................................................................... 25
4.10 Reset Password............................................................................................................ 26

5 Groups ................................................................................................................................... 28
5.1 Get All Groups ................................................................................................................ 28
5.2 Get Group Details ........................................................................................................... 29
5.3 Create Group .................................................................................................................. 31
5.4 Update Group - Basic ..................................................................................................... 32
5.5 Update Group - Full ........................................................................................................ 34
5.6 Delete Groups................................................................................................................. 35
5.7 Browse AD Groups ......................................................................................................... 37
5.8 Import Groups from AD................................................................................................... 37

6 Roles ...................................................................................................................................... 39
6.1 Get All Roles ................................................................................................................... 39
6.2 Get Role Details.............................................................................................................. 41
6.3 Create Role..................................................................................................................... 41
6.4 Update Role .................................................................................................................... 42
6.5 Delete Roles ................................................................................................................... 44

7 UMC APIs Error Codes ......................................................................................................... 46

User Management Component 1.9 - UMC Service Layer API Developer Manual
iii
A5E39179405-AC
1 What is UMC Service Layer?
UMC Service Layer (SL) is the UMC Open Development Kit (ODK) to develop an application that
needs to manage authentication, UMC users, groups and roles. Refer to the User Management
Component Installation Manual for more details on the UMC Service Layer configuration.

UMC SL is based on HTTP services that reach a broad range of clients, including browsers and mobile
devices. It can be used to develop Web pages and is also a powerful platform for exposing APIs
providing services and data. HTTP is simple, flexible and ubiquitous. Almost any platform that you can
think of has an HTTP library.

The data exchange is based on JSON format. Any call to the UMC SL include the requested "method"
in the uri or the HTTP request. The response format is composed of:

• a common part that includes operation and protocol information;

• a detailed part that is described in each API.

For a complete list of the exposed APIs see:

• authentication APIs;
• user management APIs;
• group management APIs.

Any request except the ones necessary to login, needs authorization. Authorization session is created
using one of the "authentication" methods and transmitted by the browser in the request header
(cookie authentication).

User Management Component 1.9 - UMC Service Layer API Developer Manual
4
A5E39179405-AC
2 Common Response Information
The answer for every response (except the service for WebSSO) has the following format.

Response Header Fields

Field Value

status • 200 in case of success;

• 4xx otherwise.

Content-Type application/json

Response JSON Example

"Version": 0 //the version of the protocol

"operation": "usersresult" // identify the operation called by the API
"result": 0

Response JSON Description

Property Type Description

version integer Protocol version. Consider that can vary depending on the API. See each API
section for the value.

operation string Represents the invoked operation. See each API section for the value.

result integer Returns the last error code (decimal format) returned by the UMC APIs invoked
during the command execution. See UMC APIs Error Codes for more details.

User Management Component 1.9 - UMC Service Layer API Developer Manual
5
A5E39179405-AC
3 Authentication
The following APIs are dedicated to authentication:

• Login
• Authentication from Claim

3.1 Login
Performs user authentication providing a user name and password.

example URL https://localhost/UMC/slwapi/login

Request HTTP Verb POST

Request Content-Type application/x-www-form-urlencoded

Request Parameters The following parameters must be provided.

Name Type Description

user string User name.

password string User password.

Example:
https://localhost/UMC/slwapi/login?user=myuser&password=mypsw

Response JSON Example

{"version" : 0 ,
"operation" : "loginresult",
"result" : 0}

Response JSON Description

For the common properties see Common Response Information.

Example: REST call

function CallLogin([string]$protocol,[string]$srv,[string]$user,[string]$pwd)

User Management Component 1.9 - UMC Service Layer API Developer Manual
6
A5E39179405-AC
 3 Authentication
3.1 Login

{
write-host "Call login to service layer"
write-host "Server:$srv"
write-host "user:$user"

$url = $protocol+"://"+$srv+"/UMC/slwapi/login"
$uri = New-Object "System.Uri" "$url"
$request = [System.Net.HttpWebRequest]::Create($uri)
$pair = "user=$user&password=$pwd"
$enc = [system.Text.Encoding]::UTF8
$data = $enc.GetBytes($pair)
$request.ContentType = "application/x-www-form-urlencoded"
$request.cookiecontainer = New-Object System.Net.CookieContainer
$request.Method = "POST"
$stream= $request.GetRequestStream()
$stream.Write($data,0,$data.Length)
$stream.Flush()
$stream.close()
$response = $request.GetResponse()
if ($response.StatusCode -eq "OK" )
{
$cookie = $response.Cookies[0]
$resstream= $response.GetResponseStream()
$streanreader = New-Object System.IO.StreamReader($resstream)
$logindata = $streanreader.ReadToEnd()
write-host $logindata
write-host $cookie
return $cookie
}
return $null
}

Input Parameters

The input parameters of this function are the following:

• the http or https protocol,

• the server to be used for the REST call,
• the user name and password for the login.

Return Values

• NULL if the login is not successful,

• the cookie if the login is successful.

The function also writes the result JSON shown in the example.

User Management Component 1.9 - UMC Service Layer API Developer Manual
7
A5E39179405-AC
3 Authentication
3.2 Authentication from Claim

3.2 Authentication from Claim

Performs the authentication of a user providing a claim. The user and the signature that guarantee
claim validity are given in input. This user must have the proper function right (UM_ADMIN or
UM_CLAIMAUTH). The name and the password in input are the credentials of the user that
guarantees the claim validity and NOT the one of the user requesting authentication.

example URL https://localhost/UMC/slwapi/pswclaimlogin

Request POST
HTTP Verb

Request application/x-www-form-urlencoded
Content-
Type

Request The following parameters must be provided.

Parameters Name Type Description

name string Name of the guaranteeing user.

password string Password of the guaranteeing user.

claim string Claim of the authenticating user.

signature string Claim signature.

keyid string The identifier of the key used to sign the claim.

Example:
https://localhost/UMC/slwapi/pswclaimlogin?name=myuser&password=
mypsw&claim=myclaim&signature=mysignature&keyid=mykeyid

User Management Component 1.9 - UMC Service Layer API Developer Manual
8
A5E39179405-AC
4 Users
The following APIs are dedicated to user management:

• Get All Users

• Get User Details
• Create a user
• Update User - Basic
• Update User - Full
• Unlock User
• Delete Users
• Browse AD Users
• Import Users from AD

4.1 Get All Users

Returns data related to all UMC users.

example URL https://localhost/UMC/slwapi/users

Request HTTP Verb POST

Request Content-Type application/json

Request Parameters None.

Response JSON Example

{
"version":0,
"operation":"usersresult",
"result":0,
"users":
[
{"id": 2,"objver":1,"name":"root","fullname":"","comment":"","userflags":
8},
{"id": 1073741852, "objver":2,"name":"umdom1\\administrator",
"fullname":"Administrator","comment":"Built-in account for
administering the computer\/domain","userflags":24},
{"id": 29,"objver":1,"name":"Marco", "fullname": "Marco Rossi","comment":
"this user can change the password","userflags":10},
{"id": 30,"objver":2,"name":"Luca", "fullname": "Luca Bianchi",
"comment":"this user is locked", "userflags":12},

User Management Component 1.9 - UMC Service Layer API Developer Manual
9
A5E39179405-AC
4 Users
4.1 Get All Users

{"id": 31,"objver":2,"name": "Isa","fullname": "Isa Verdi","comment":

"this user must change the password", "userflags":9},
{"id":1073741851, "objver":2,"name":"VM-UMC-11\\Administrator",
"fullname": "","comment":"","userflags":40}
]
}

Response JSON Description

For the common properties see Common Response Information.

users property Array

Each user object has the following properties:

Property Type Description

id integer User identifier, it is a 32 bit number greater than zero where the 31st bit is used
to store the information if the user is imported or not. If the 31st bit is equal to 1
the user is imported from Active Directory, 0 otherwise. The ID ranges are as
follows:
• 1-20: reserved to system users;
• 21- 1073741844: UMC users created from scratch;
• 1073741845 to 2147483647: UMC users imported from Active Directory.

objver integer This is an integer that is incremented at each user modification.

name string User name.

fullname string User full name.

comment string A note that can be added to the user (optional).

User Management Component 1.9 - UMC Service Layer API Developer Manual
10
A5E39179405-AC
 4 Users
4.2 Get User Details

Property Type Description

userflags integer It is a 16 bit number bit mask representing the following flags, the order is from
the LSB (less significant bit) to the MSB (most significant bit) :
1. User Must Change Password: it is equal to 1 if the user must change
password, 0 otherwise.
2. User Can Change Password: it is equal to 1 if the user can change
password, 0 otherwise.
3. User Locked: it is equal to 1 if the user is locked, 0 otherwise.
4. User Enabled: it is equal to 1 if the user can authenticate into UMC, 0
otherwise.
5. User imported from AD: it is equal to 1 if the user has been imported
from Active Directory domain users, 0 otherwise.
6. User imported from Local: it is equal to 1 if the user has been imported
from Windows local users, 0 otherwise.
7. User imported from group: it is equal to 1 if the user has been imported
through imported Active Directory group, 0 otherwise.
8. User offline: it is equal to 1 if the user is offline, 0 otherwise. See Get
User Details for additional information.
9. Not used.
10. Not used.
11. Not used.
12. Not used.
13. Not used.
14. Not used.
15. Not used.
16. Not used.

4.2 Get User Details

Returns all the details related to the user associated with the input id.

example URL https://localhost/UMC/slwapi/users{/id}

Request HTTP Verb POST

Request Content-Type application/json

Request Parameters None.

Response JSON Example

User Management Component 1.9 - UMC Service Layer API Developer Manual
11
A5E39179405-AC
4 Users
4.2 Get User Details

"version": 140,
"operation": "usersresult",
"result": 0,
"users": {
"id": 25,
"objver":16,
"name": "mydomain\myName",
"fullname": "my fullname",
"comment": "",
"firstname": "myFirstname",
"lastname": "myLastname",
"initials": "MI",
"language": "IGNORE_CULT",
"datalanguage": "IGNORE_CULT",
"phone": "",
"mobile": "",
"email1": "",
"email2": "",
"email3": "",
"sid": "",
"expirationdate": "never expire",
"alertsbeforeexpirationdate": "no allert",
"passwordexpirationdays": "password never expire",
"alertbeforepasswordexpirationdays": "no allert",
"autologoff": "no autologoff",
"timebeforeautologoff": "no autologoff",
"imported": 1,
"enabled": 1,
"locked": 1,
"mustchange": 1,
"offline": 1,
"importedfromgroup": 0 ,
"importedfromad": 1 ,
"canchange": 1,
"attributes": [
{
"name": "attr_1",
"value": "val_1"
},
{
"name": "attr_2",
"value": "val_2"
}

],
"roles": [
{
"name": "role_1",
"id": 21,
"description": "role_1 "
},
{

User Management Component 1.9 - UMC Service Layer API Developer Manual
12
A5E39179405-AC
 4 Users
4.2 Get User Details

"name": "role_2",
"id": 22,
"description": "role_2 "
},
{
"name": "role_3",
"id": 23,
"description": "role_3 "
}
],
"groups": [
{
"name": "group1",
"id": 1,
"imported": 1,
"objver":60,
"sid":"",
"description": "descr_1 "
},
{
"name": "group2",
"id": 2,
"imported": 1,
"objver":60,
"sid":"",
"description": "descr_2 "
}
]
}
}

Response JSON Description

For the common properties see Common Response Information.

users Object

The user object has the following properties:

User Management Component 1.9 - UMC Service Layer API Developer Manual
13
A5E39179405-AC
4 Users
4.2 Get User Details

Property Type Description

id integer User identifier, it is a 32 bit number greater than

zero where the 31st bit is used to store the
information if the user is imported or not. If the 31st
bit is equal to 1 the user is imported from Active
Directory, 0 otherwise. The ID ranges are as
follows:
• 1-20: reserved to system users;
• 21- 1073741844: UMC users created from
scratch;
• 1073741845 to 2147483647: UMC users
imported from Active Directory.

objver integer This is an integer that is incremented at each user

modification.

name string User name.

fullname string User full name.

comment string A note that can be added to the user (optional).

firstname string User first name.

lastname string User last name.

initials string User initials.

language string It is the user language and has the format

<langcode>-<countrycode>, where
• langcode is the language code according to
the ISO 639 standard; we accept both two-
letter codes (ISO 639-1) and three-letter
codes (ISO 639-2);
• countrycode is the country code according to
the ISO 3166 standard.
An example is en-GB.

datalanguage string It is the language in which are displayed the user

data, see above for the language.

phone string User phone number.

mobile string User mobile phone number.

email1 string First user email address.

email2 string Additional email address for the user.

email3 string Additional email address for the user.

sid string User Security Identifier (SID). See Microsoft

Documentation on Security Identifiers for more
details.

expirationdate string The date in which the user expires.

User Management Component 1.9 - UMC Service Layer API Developer Manual
14
A5E39179405-AC
 4 Users
4.2 Get User Details

Property Type Description

alertsbeforeexpirationdate string It is the number of days from which a warning

appears to the user notifying him/her about the user
expiration.

passwordexpirationdays string It is the number of days for which the password is

valid.

alertbeforepasswordexpirationdays string It is the number of days from which a warning

appears to the user notifying him/her about the
password expiration.

autologoff string It is equal to TRUE if the user automatic logoff is

enabled, FALSE otherwise.

timebeforeautologoff string It is the number of minutes that must elapse before

a user is automatically logged off from the system
(session-based).

imported integer It is equal to 1 if the user has been imported from

Windows local users, 0 otherwise.

enabled integer It is equal to 1 if the user can authenticate into

UMC, 0 otherwise.

locked integer It is equal to 1 if the user is locked, 0 otherwise.

mustchange integer It is equal to 1 if the user must change password, 0

otherwise.

offline integer It is equal to 1 if the user is offline, 0 otherwise.

When creating a user, you can flag it as offline.
UMC provisioning service checks if the offline user
exists in Active Directory:
• if the user is present, user data are
synchronized and the user becomes online,
• otherwise the user remains offline.
The user name of offline users must follow the AD
pattern <domainName>\<ADuserName> . They do
not have a UMC password, as they cannot
authenticate until they become online.

importedfromgroup integer It is equal to 1 if the user has been imported

through imported Active Directory group, 0
otherwise.

importedfromad integer It is equal to 1 if the user has been imported from

Active Directory domain users, 0 otherwise.

canchange integer It is equal to 1 if the user can change password, 0

otherwise.

attributes property Array

Each attribute object has the following properties:

User Management Component 1.9 - UMC Service Layer API Developer Manual
15
A5E39179405-AC
4 Users
4.3 Create User

Property Type Description

name string Attribute name.

value string Attribute value.

roles property Array

Each role object has the following properties:

Property Type Description

name string Role name.

id string Role identifier.

description string Role description.

groups property Array

Each group object has the following properties:

Property Type Description

name string Group name.

id string Group identifier.

imported integer It is equal to 1 if the group is imported from Active Directory or from local, 0
otherwise.

objver integer This is an integer that is incremented at each user modification.

sid NA Group Security Identifier (SID). See Microsoft Documentation on Security

Identifiers for more details

description string Group description.

4.3 Create User

Creates a new user. In case of success the object is returned including the assigned id.

example URL https://localhost/UMC/slwapi/users/add

Request HTTP Verb POST

Request Content-Type application/json

Request Parameters None.

User Management Component 1.9 - UMC Service Layer API Developer Manual
16
A5E39179405-AC
 4 Users
4.3 Create User

Request JSON Example

It is optional. It is mandatory only if parameters in the query string are not present.

If the user is offline, the value of the offline property assumes the value true that corresponds to 1. If
the user is not offline, the offline property is not part of the JSON file. The meaning is the same as
described in Get User Details. Empty passwords are not allowed.

[{"name":"franz",
"password":"secret",
"fullname":"franz",
"canchange":true,
"mustchange":false,
"enabled":true,
"locked":false,
"offline":true}]

Request JSON Description

For the description of the single user properties see Get User Details.

Response JSON Example

{
"version": 0 ,
"operation" : "useraddresult",
"result" : 0, users: [{
"id" = 102, //present only in case of success
"result" = 0,
"name" = "franz",
"offline" = true,
"password" = "secret",
"fullname" = "franz",
"canchange" = true,
"mustchange" = false,
"enabled" = true,
"locked" = false}]
}

Response JSON Description

For the common properties see Common Response Information. For the description of the single user
properties see Get User Details. See above for the management of the offline property.

User Management Component 1.9 - UMC Service Layer API Developer Manual
17
A5E39179405-AC
4 Users
4.4 Update User - Basic

4.4 Update User - Basic

Updates the following basic user properties:

• fullname
• password (empty passwords are not allowed)
• enabled
• mustchange
• canchange

example URL https://localhost/UMC/slwapi/users/updateinline

Request HTTP Verb POST

Request Content-Type application/json

Parameters None.

Request JSON Example

[
{"id":10247,
"name":"myName",
"objver":19,
"fullname":"user new fullname",
"password":"secret",
"canchange":1,
"mustchange":0,
"enabled":1,
"locked":0}
]

Request JSON Description

For the description of the single user properties see Get User Details.

Response JSON Example

{ "version" : 0,
" operation" : "userupdateresult",
"result" : 0,
"users": [
{"canchange": 1,

User Management Component 1.9 - UMC Service Layer API Developer Manual
18
A5E39179405-AC
 4 Users
4.5 Update User - Full

"enabled": 1,
"fullname": "user new fullname",
"id": 10247,
"locked":0,
"mustchange": 0,
"name": "myName",
"objver": 20,
"password": "secret",
"result":0}
]
}

Response JSON Description

For the common properties see Common Response Information. For the description of the single user
properties see Get User Details.

4.5 Update User - Full

Performs a full update of a user. All the modifiable user properties can be updated.

example URL https://localhost/UMC/slwapi/users/update

Request HTTP Verb POST

Request Content-Type application/json

Request Parameters None.

Request JSON Example

[
{
"id":5037,
"objver":2,
"name":"Alessio",
"fullname":"ROSSI ALESSIO",
"comment":"GOOD",
"initials":"AR",
"datalanguage":"en-GB",
"language":"en-GB",
"firstname":"Alessio",
"lastname":"Rossi",
"mobile":"",
"phone":"",

User Management Component 1.9 - UMC Service Layer API Developer Manual
19
A5E39179405-AC
4 Users
4.5 Update User - Full

"email1":"",
"email2":"",
"email3":"",
"enabled":1,
"locked":0,
"canchange":1,
"mustchange":0,
"alertbeforepasswordexpirationdays":"0",
"passwordexpirationdays":"0",
"override_lock_policy":0,
"alertsbeforeexpirationdate":"0",
"autologoff":"30",
"timebeforeautologoff":"3",
"expirationdate":"Sun, 29 Nov 2076 08:54:34 GMT",
"attributes":[
{ "name":"Address",
"value":"Trafalgar Square 1a" }
],
"groups": [ ],
"roles":[
{"name":"myrole",
"id":21,
"description":"myroledescription"}
]
}
]

Request JSON Description

For the description of the single user properties see Get User Details.

Response JSON Example

{
"version" : 0 ,
"operation" : "userupdateresult",
"result" : 0,
"users":[
{"alertbeforepasswordexpirationdays":"0",
"alertsbeforeexpirationdate":"0",
"attributes":
[ { "name":"Address",
"value":"Trafalgar Square 1a" }
],
"autologoff":"30",
"canchange":1,
"comment":"GOOD",

User Management Component 1.9 - UMC Service Layer API Developer Manual
20
A5E39179405-AC
 4 Users
4.6 Unlock User

"datalanguage":"en-GB",
"email1":"",
"email2":"",
"email3":"",
"enabled":1,
"expirationdate":"Sun, 29 Nov 2076 08:54:34 GMT",
"firstname":"Alessio",
"fullname":"ROSSI ALESSIO",
"groups":[],
"id":5037,
"initials":"AR",
"language":"en-GB",
"lastname":"Rossi",
"locked":0,
"mobile":"+393211233210",
"mustchange":0,
"name":"Alessio",
"objver":3,
"override_lock_policy":0,
"password":null,
"passwordexpirationdays":"0",
"phone":"0101112223",
"result":0,
"roles":[
{"description":"myroledescription1",
"id":21,
"name":"myrole"}
],
"timebeforeautologoff":"3"}
]
}

Response JSON Description

For the common properties see Common Response Information. For the description of the single user
properties see Get User Details.

4.6 Unlock User

Unlocks a user.

example URL https://localhost/UMC/slwapi/users/unlock

Request HTTP Verb POST

Request Content-Type application/json

Parameters None.

User Management Component 1.9 - UMC Service Layer API Developer Manual
21
A5E39179405-AC
4 Users
4.7 Delete Users

Request JSON Example

{
name=newuser
}

Request JSON Description

For the description of the single user properties see Get User Details.

Response JSON Example

{
"version" : 0 ,
"operation" : "userunlockresult",
"result" : 0}

Response JSON Description

For the common properties see Common Response Information.

4.7 Delete Users

Deletes a list of users.

example URL https://localhost/UMC/slwapi/users/delete{/id}

Request HTTP Verb POST

Request Content-Type application/json

Request Parameters None.

Request JSON Example

Optional. Mandatory only if id is not present.

[
{"id":5034}

User Management Component 1.9 - UMC Service Layer API Developer Manual
22
A5E39179405-AC
 4 Users
4.8 Browse AD Users

Request JSON Description

For the description of the single user properties see Get User Details.

Response JSON Example

{
"deleted":[{
"id":5034,
"result":0}],
"operation":"deleteresponse",
"result":0,
"version":0}

Response JSON Description

For the common properties see Common Response Information.

deleted property Array

Each deleted object has the following properties:

Property Type Description

id integer Identifier of the user that has been deleted.

result N/A See Common Response Information.

4.8 Browse AD Users

Browses the users in the UMC database that have been imported from Active Directory (AD).

example URL https://localhost/UMC/slwapi/adusers{/s*}

Request HTTP Verb POST

Request Content- application/json

Type

User Management Component 1.9 - UMC Service Layer API Developer Manual
23
A5E39179405-AC
4 Users
4.8 Browse AD Users

example URL https://localhost/UMC/slwapi/adusers{/s*}

Request Parameters The search string.

Example: https://localhost/UMC/slwapi/adusers/user*
The service finds all users that match the string user* in the username
field.

Response JSON Example

{
"version": 0,
"operation": "adusersresult",
"result": 0,
"users": [
{
"comment": "my comment 1",
"email1": "[email protected]",
"firstname": "Firstname1",
"fullname": "Fullname of user 1",
"lastname": "Lastname1",
"mobile": "",
"phone": "",
"sid": "S-1-5-21-1972147420-2157339849-452057256-3749",
"username": "domain\\USER1"
},
{
"comment": "my comment 2",
"email1": "[email protected]",
"firstname": "Firstname2",
"fullname": "Fullname of user 2",
"lastname": "Lastname2",
"mobile": "",
"phone": "",
"sid": "S-1-5-21-1972147420-2157339849-452057256-3753",
"username": "domain\\USER2"
},
{
"comment": "my comment 3",
"email1": "[email protected]",
"firstname": "Firstname3",
"fullname": "Fullname of user 3",
"lastname": "Lastname3",
"mobile": "",
"phone": "",
"sid": "S-1-5-21-1972147420-2157339849-452057256-4077",
"username": "domain\\USER3"
},
]
}

User Management Component 1.9 - UMC Service Layer API Developer Manual
24
A5E39179405-AC
 4 Users
4.9 Import Users from AD

Response JSON Description

In case of success an array of user objects, including the assigned identifiers, is returned. For the
common properties see Common Response Information. For the description of the single user
properties see Get User Details.

4.9 Import Users from AD

Imports users from Active Directory (AD).

example URL https://localhost/UMC/slwapi/users/import

Request HTTP Verb POST

Request Content-Type application/json

Request Parameters None.

Request JSON Example

[{
"comment":"my comment",
"company":"my company",
"email1":"[email protected]",
"firstname":"username_first",
"fullname":"username_full",
"lastname":"username_last",
"mobile":"",
"phone":"",
"sid":"S-1-5-21-1972147420-2157339849-452057256-3753",
"username":"SWQA\\ITA00",
"selected":true,
"id":1
}]

Request JSON Description

For the description of the single user properties see Get User Details.

Response JSON Example

{}

User Management Component 1.9 - UMC Service Layer API Developer Manual
25
A5E39179405-AC
4 Users
4.10 Reset Password

4.10 Reset Password

Performs the password reset of a specified user. The new password must not necessarily conform to
the Global Account Policy Properties. For more details on these properties, see User Management
Component API SDK Developer Manual.

The user performing the action is represented by the input identity handle parameter and must have
the function right UM_ADMIN or both the function rights UM_VIEW and UM_RESETPSW. For a
detailed list of UM function rights, see the Appendix of User Management Component API SDK
Developer Manual.

Empty passwords are not allowed.

example URL https://localhost/UMC/slwapi/resetpsw

Request HTTP Verb POST

Request Content-Type application/json

Request Parameters None.

Request JSON Example

[{"usertoreset" = "franz",
"pswtoreset" = "secret"}]

Request JSON Description

Property Type Description

usertoreset string Name of the user whose password has to be reset.

pswtoreset string The new value of the password.

Response JSON Example

{
"version": 0 ,
"operation" : "pswresetresult",
"result" : 0
}

User Management Component 1.9 - UMC Service Layer API Developer Manual
26
A5E39179405-AC
 4 Users
4.10 Reset Password

Response JSON Description

For the common properties see Common Response Information.

User Management Component 1.9 - UMC Service Layer API Developer Manual
27
A5E39179405-AC
5 Groups
The following APIs are dedicated to group management:

• Get All Groups

• Get Group Details
• Create Group
• Update Group - Basic
• Update Group - Full
• Delete Groups
• Browse AD Groups
• Import Groups from AD

5.1 Get All Groups

Returns data related to all UMC groups.

example URL https://localhost/UMC/slwapi/groups

Request HTTP Verb POST

Request Content-Type application/json

Request Parameters None.

Response JSON Example

{
"version" : 140 ,
"operation" : "groupsresult",
"result" : 0,

"groups" : [{
"description":"mygroupdescription",
"id":628,
"imported":0,
"name":"mygroup",
"objver":0,
"offline":0,
"sid":""},

{
"description":"mygroupdescription1",

User Management Component 1.9 - UMC Service Layer API Developer Manual
28
A5E39179405-AC
 5 Groups
5.2 Get Group Details

"id":629,
"imported":0,
"name":"mygroup1",
"objver":0,
"offline":1,
"sid":""}]
}

Response JSON Description

For the common properties see Common Response Information.

groups property Array

Each group object has the following properties:

Property Type Description

description string Group description.

id integer Group identifier.

imported integer It is equal to 1 if the group is imported from Active Directory, 0 otherwise.

name string Group name.

objver integer This is an integer that is incremented at each modification.

offline integer It is equal to 1 if the group is offline, 0 otherwise.

When creating a group, you can flag it as offline. UMC provisioning service
checks if the offline group exists in Active Directory:
• if the group is present, group data are synchronized, the AD users
members of the groups are imported into UMC and the group becomes
online,
• otherwise the group remains offline.
The group name of offline users must follow the AD pattern <domainName>\
<ADgroupName> .

sid string Group Security Identifier (SID). See Microsoft Documentation on Security
Identifiers for more details

5.2 Get Group Details

Returns all the details related to the group associated to the input id.

example URL https://localhost/UMC/slwapi/groups/{/id}

Request HTTP Verb POST

User Management Component 1.9 - UMC Service Layer API Developer Manual
29
A5E39179405-AC
5 Groups
5.2 Get Group Details

Request Content-Type application/url-encoding

Request Parameters None.

Response JSON Example

{
"version" : 0 ,
"operation" : "groupsresult",
"result" : 0,
"group" : {
"name":"mygroup",
"id" : 628,
"imported" : 0,
"offline" : 0,
"objver" : 1,
"description" : "mygroupnewdescription",
"lastsync" : 0,
"syncstatus" : "SYNC_NOSTATUS",
"sid" : "",
"roles":[{
"name":"myrole",
"id" : 21,
"description" : "myroledescription"
}],
"users":[]
}}

Response JSON Description

For the common properties see Common Response Information.

group Object

The group object has the following properties:

Property Type Description

name string Group name.

id integer Group identifier.

imported integer It is equal to 1 if the group is imported from Active Directory, 0 otherwise.

User Management Component 1.9 - UMC Service Layer API Developer Manual
30
A5E39179405-AC
 5 Groups
5.3 Create Group

Property Type Description

offline integer It is equal to 1 if the group is offline, 0 otherwise.

When creating a group, you can flag it as offline. UMC provisioning service
checks if the offline group exists in Active Directory:
• if the group is present, group data are synchronized, the AD users
members of the groups are imported into UMC and the group becomes
online,
• otherwise the group remains offline.
The group name of offline users must follow the AD pattern <domainName>\
<ADgroupName> .

objver integer This is an integer that is incremented at each modification.

description string Group description.

lastsync N/A Not used.

syncstatus N/A Not used.

sid string Group Security Identifier (SID). See Microsoft Documentation on Security
Identifiers for more details

roles property Array

Each role object has the following properties:

Property Type Description

name string Role name.

id string Role identifier.

description string Role description.

5.3 Create Group

Creates a new group. In case of success the object is returned including the assigned id.

example URL https://localhost/UMC/slwapi/groups/add

Request HTTP Verb POST

Request Content-Type application/json

Request Parameters None.

User Management Component 1.9 - UMC Service Layer API Developer Manual
31
A5E39179405-AC
5 Groups
5.4 Update Group - Basic

Request JSON Example

[
{"name":"mygroup",
"domain":"",
"description":"mygroupdescription",
"offline":true
}]

Request JSON Description

For the description of the single group properties see Get Group Details.

If the group is offline, the value of the offline property assumes the value true that corresponds to 1. If
the group is not offline, the offline property is not part of the JSON file. The meaning is the same as
described in Get Group Details.

Response JSON Example

{
"groups":[{
"description":"mygroupdescription",
"domain":"",
"id":628,
"name":"mygroup",
"result":0}],
"operation":"useraddgroup",
"offline":true,
"result":0,
"version":0}

Response JSON Description

For the common properties see Common Response Information. For the description of the single user
properties see Get Group Details. See above for the management of the offline property.

5.4 Update Group - Basic

Updates the following basic user properties:

• name,
• domain,

User Management Component 1.9 - UMC Service Layer API Developer Manual
32
A5E39179405-AC
 5 Groups
5.4 Update Group - Basic

• description.

example URL https://localhost/UMC/slwapi/groups/updateinline

Request HTTP Verb POST

Request Content-Type application/json

Request Parameters None.

Request JSON Example

[{
"id":628,
"name":"mygroup",
"domain":"UMC",
"description":"mygroupnewdescription"
}]

Request JSON Description

For the description of the single group properties see Get Group Details.

Response JSON Example

{
"groups":[{
"description":"mygroupnewdescription",
"domain":"UMC",
"id":628,
"name":"mygroup",
"objver":0,
"result":0}],
"operation":"userupdateinlinegroup",
"result":0,
"version":0}

Response JSON Description

In case of success the object is returned including the assigned id. For the common properties see
Common Response Information. For the description of the single group properties see Get Group
Details.

User Management Component 1.9 - UMC Service Layer API Developer Manual
33
A5E39179405-AC
5 Groups
5.5 Update Group - Full

5.5 Update Group - Full

Performs a full update of a group. All the modifiable group properties can be updated.

example URL https://localhost/UMC/slwapi/groups/update

Request HTTP Verb POST

Request Content-Type application/json

Request Parameters None.

Request JSON Example

[{
"name":"mygroup",
"id":628,
"imported":0,
"objver":1,
"offline":0,
"description":"mygroupnewdescription",
"lastsync":0,
"syncstatus":"SYNC_NOSTATUS",
"sid":"",
"roles":[{
"name":"myrole",
"id" : 21,
"description" : "myroledescription"
}],
"users":[{
"id":5034,
"name":"nuovo",
"fullname":"nuovo"}],
"rights":{
"can_modify":true,
"can_read":true,
"can_resetpwd":true,
"can_unlock":true,
"is_admin":true}
}]

Response JSON Description

For the description of the single user properties see Get Group Details.

User Management Component 1.9 - UMC Service Layer API Developer Manual
34
A5E39179405-AC
 5 Groups
5.6 Delete Groups

Response JSON Example

{
"groups":[{
"description":"mygroupnewdescription",
"id":628,
"imported":0,
"lastsync":0,
"name":"mygroup",
"objver":1,
"offline":0,
"result":0,
"rights":{
"can_modify":true,
"can_read":true,
"can_resetpwd":true,
"can_unlock":true,
"is_admin":true},
"roles":[{
"description":"myroledescription",
"id":21,
"name":"myrole"
}]
"sid":"",
"syncstatus":"SYNC_NOSTATUS",
"users":[{
"fullname":"nuovo",
"id":5034,
"name":"nuovo"}]
}],
"operation":"userupdategroup",
"result":0,
"version":0}

Response JSON Description

For the common properties see Common Response Information. For the description of the single user
properties see Get Group Details.

5.6 Delete Groups

Deletes a list of groups.

example URL https://localhost/UMC/slwapi/groups/delete

Request HTTP Verb POST

User Management Component 1.9 - UMC Service Layer API Developer Manual
35
A5E39179405-AC
5 Groups
5.6 Delete Groups

Request Content-Type application/json

Request Parameters None.

Request JSON Example

[{
"id":628
}]

Request JSON Description

For the description of the single group properties see Get Group Details.

Response JSON Example

{
"groups":[{
"id":628,
"result":0}],
"operation":"deletegroupresponse",
"result":0,
"version":0}

Response JSON Description

In case of success the object is returned including the assigned id. For the common properties see
Common Response Information.

groups property Array

Each groups object has the following properties:

Property Type Description

id integer Identifier of the group that has been deleted.

result N/A See Common Response Information.

User Management Component 1.9 - UMC Service Layer API Developer Manual
36
A5E39179405-AC
 5 Groups
5.7 Browse AD Groups

5.7 Browse AD Groups

Browses the groups in the UMC database that have been imported from Active Directory (AD).

example URL https://localhost/UMC/slwapi/adgroups{/s*}

Request HTTP Verb POST

Request Content- application/json

Type

Request Parameters The search string.

Example: https://localhost/UMC/slwapi/adgroups/umc*
The service finds all groups that match the string umc* in the groupname
field.

Response JSON Example

{
"version" : 0,
"operation" : "adgroupsresult",
"result" : 0,
"groups":[
{"description":"vdi_P13_UMC","domain":"MYDOMAIN","name":"vdi_P13_UMC",
"sid":"S-1-5-21-1972147420-2157339849-452057256-14151"},
{"description":"SWQA UMC","domain":"MYDOMAIN","name":"SWQA UMC","sid":
"S-1-5-21-1972147420-2157339849-452057256-13147"},
{"description":"SWQA UMC read","domain":"MYDOMAIN","name":"SWQA UMC
read","sid":"S-1-5-21-1972147420-2157339849-452057256-15002"}
]
}

Response JSON Description

In case of success an array of groups objects, including the assigned identifiers, is returned. For the
common properties see Common Response Information. For the description of the single user
properties see Get Group Details.

5.8 Import Groups from AD

Imports groups from Active Directory (AD).

example URL https://localhost/UMC/slwapi/groups/import

Request HTTP Verb POST

User Management Component 1.9 - UMC Service Layer API Developer Manual
37
A5E39179405-AC
5 Groups
5.8 Import Groups from AD

Request Content-Type application/json

Request Parameters None.

Request JSON Example

[{"description":"SWQA UMC read",

"domain":"SWQA",
"name":"SWQA UMC read",
"sid":"S-1-5-21-1972147420-2157339849-452057256-15002",
"selected":true}]

Request JSON Description

For the description of the single user properties see Get Group Details.

Response JSON Example

{"version" : 0,
"operation" : "groupimportresult",
"result" : 0,
"groups":[
{"description":"SWQA UMC read",
"domain":"SWQA",
"name":"SWQA UMC read",
"result":13,
"selected":true,
"sid":"S-1-5-21-1972147420-2157339849-452057256-15002"
}]}

JSON Description

For the common properties see Common Response Information. For the description of the single user
properties see Get Group Details.

User Management Component 1.9 - UMC Service Layer API Developer Manual
38
A5E39179405-AC
6 Roles
The following APIs are dedicated to role management:

• Get All Roles

• Get Role Details
• Create Role
• Update Role
• Delete Roles

6.1 Get All Roles

Returns data related to all UMC roles.

example URL https://localhost/UMC/slwapi/roles

Request HTTP Verb POST

Request Content-Type application/json

Request Parameters None.

Response JSON Example

{
"Version": 0,
"operation": "rolesresult",
"result": 0,
"roles":
[
{"id": 2,"name": "administrator","description": "","application":
"UMC","function_rights": "all" },
{"id": 21,"name": "Reader","description": "Only Read","application":
"UMC","function_rights": []}
{"id": 22,"name": "Writer","description": "Write","application": "UMC",

"function_rights":
[
{ "name":"UM_ADMIN", "id" : 10001, "description" : "Administer UM
Configuration" },
{ "name":"UM_VIEW", "id" : 10002, "description" : "View UM
Configuration" },
{ "name":"UM_RESETPWD", "id" : 10003, "description" : "Reset user
password" },

User Management Component 1.9 - UMC Service Layer API Developer Manual
39
A5E39179405-AC
6 Roles
6.1 Get All Roles

{ "name":"UM_RA", "id" : 10004, "description" : "Login from Remote

Authentication" },
{ "name":"UM_UNLOCKUSR", "id" : 10005, "description" : "Unlock User"
},
{ "name":"UM_JOIN", "id" : 10006, "description" : "Create UM Server"
}
]
}
]
}

Response JSON Description

For the common properties see Common Response Information.

roles property Array

Each role object has the following properties:

Property Type Description

id integer Role identifier. 0 and negative IDs are not allowed. The ID ranges are as
follows:
• 1-20: reserved to system roles;
• 21-32600: UMC roles created from scratch.

name string Role name.

description string Role description.

application - Not used.

function_rights function The set of function rights associated to the role. If the role has no
right associated function rights the value is [], if the role has all the associated
Array function rights the value is all, this is the case of the Administrator built-
in role. See below for the description of the function right object
properties.

function rights property Array

Each function right object has the following properties:

Property Type Description

name string Function right name.

id integer Function right identifier.

description string Function right description.

User Management Component 1.9 - UMC Service Layer API Developer Manual
40
A5E39179405-AC
 6 Roles
6.2 Get Role Details

6.2 Get Role Details

Returns all the details related to the role associated with the input id.

example URL https://localhost/UMC/slwapi/roles/{/id}

Request HTTP Verb POST

Request Content-Type application/json

Request Parameters None.

Response JSON Example

{
"version" : 0 ,
"operation" : "roledetailresult",
"result" : 0,
"role" :
{
"name":"myrole",
"objver": 6,
"id" : 21,
"application" : "UMC",
"description" : "myroledescription1a",
"function_rights" : ["name":"UM_VIEW","id" : 10002,"description" :
"View UM Configuration"]
}
}

Request JSON Description

For the common properties see Common Response Information, whereas for the description of the
single role properties see Get All Roles.

6.3 Create Role

Creates a new role. In case of success the object is returned including the assigned id. The number of
roles present in the system cannot exceed 200. In addition a database constraint on the role identifiers
exists. In case you get an error message that no more role identifiers are available, to create new
roles, you have first to purge the existing one with the corresponding umconf command. See the
UMCONF User Manual for more details.

example URL https://localhost/UMC/slwapi/roles/add

User Management Component 1.9 - UMC Service Layer API Developer Manual
41
A5E39179405-AC
6 Roles
6.4 Update Role

Request HTTP Verb POST

Request Content-Type application/json

Request Parameters None.

Request JSON Example

Optional. It is mandatory only if parameters in the query string are not present.

[{"name":"myrolename",
"description":"myroledescr"}]

Request JSON Description

For the description of the single role properties see Get All Roles.

Response JSON Example

{
"operation":"addroleresult",
"roles":[{
"description":"myroledescr",
"id":21,
"name":"myrolename",
"result":0}],
"version":0
}

Response JSON Description

For the common properties see Common Response Information. For the description of the single user
properties see Get All Roles.

6.4 Update Role

Performs a full update of a role. All the modifiable role properties can be updated.

example URL https://localhost/UMC/slwapi/roles/update

Request HTTP Verb POST

User Management Component 1.9 - UMC Service Layer API Developer Manual
42
A5E39179405-AC
 6 Roles
6.4 Update Role

Request Content-Type application/json

Request Parameters None.

Request JSON Example

[{
"name":"myrole",
"objver":2,
"id":21,
"application":"UMC",
"description":"myroledescription1",
"function_rights":[{"name":"UM_ADMIN","id":10001,"description":"Administer
UM Configuration"}],
"rights":[{"name":"UM_ADMIN","id":10001,"description":"Administer UM
Configuration",own":true},
{"name":"UM_UNLOCKUSR","id":10005,"description":"Unlock User","own":
true}]
}]

Request JSON Description

For the description of the single role properties see Get All Roles.

Response JSON Example

{
"operation":"roleupdate",
"result":0,
"roles":[{
"application":"UMC",
"description":"myroledescription1",
"function_rights":[{"name":"UM_ADMIN","id":10001,"description":
"Administer UM Configuration"}],
"id":21,
"name":"myrole",
"objver":2,
"result":0,
"rights":[{
"description":"Administer UM Configuration",
"id":10001,
"name":"UM_ADMIN",
"own":true}
{
"name":"UM_UNLOCKUSR",

User Management Component 1.9 - UMC Service Layer API Developer Manual
43
A5E39179405-AC
6 Roles
6.5 Delete Roles

"id":10005,
"description":"Unlock User",
"own":true}
],
"version":0
}

Response JSON Description

For the common properties see Common Response Information. For the description of the single role
properties see Get All Roles.

6.5 Delete Roles

Deletes a list of users.

example URL https://localhost/UMC/slwapi/roles/delete{/id}

Request HTTP Verb POST

Request Content-Type application/json

Request Parameters None.

Request JSON Example

Optional. Mandatory only if id is not present.

[
{"id":22}
]

Request JSON Description

For the description of the single role properties see Get All Roles.

Response JSON Example

{
"operation":"roledelete",

User Management Component 1.9 - UMC Service Layer API Developer Manual
44
A5E39179405-AC
 6 Roles
6.5 Delete Roles

"result":0,
"roles":[{
"id":22,
"result":0}],
"version":0
}

Response JSON Description

For the common properties see Common Response Information, for the description of the single role
properties see Get All Roles.

User Management Component 1.9 - UMC Service Layer API Developer Manual
45
A5E39179405-AC
7 UMC APIs Error Codes
All the UMC APIs return a boolean value or an object handle. If the API is successful, the returned
boolean value is true or the object handle is well formed; otherwise the returned boolean value is false,
or null is returned instead of the object handle. If the API fails an error code can be retrieved calling the
SL_GetLastError method. SL_RESULT defines the type of error. In what follows we list the possible
error codes.

Generic Errors

Name Hexadecimal Value Decimal Value Description

SL_SUCCESS 0X00 0 No errors have occurred.

SL_GENERROR 0X01 1 Generic error.

SL_BAD_HANDLE 0x114 276 Internal error for invalid handle.

SL_NOSESSION 0X30 48 The Web session is expired.

Authentication Errors

Name Hexadecimal Decimal Description

Value Value

SL_USERLOCKED 0X02 2 The user for whom you want to

perform the authentication is
locked.

SL_USERDISABLED 0X03 3 The user for whom you want to

perform the authentication is
disabled.

SL_WRONGUSERNAMEPASSWORD 0X04 4 During the authentication phase,

the user name or password are
incorrect.

SL_PASSWORDPOLICYVIOLATION 0X05 5 Password policy violation

(determined by UMC account
policies). For a detailed list of
Account Policies, see User
Management Component API
SDK Developer Manual.

SL_USERMUSTCHANGEPASSWORD 0X06 6 The user password must be

changed.

SL_PASSWORDEXPIRED 0X07 7 The user password is expired.

SL_FAILED 0X0A 10 Generic operation failed.

User Management Component 1.9 - UMC Service Layer API Developer Manual
46
A5E39179405-AC
 7 UMC APIs Error Codes
6.5 Delete Roles

Name Hexadecimal Decimal Description

Value Value

SL_ALREADYLOCKED 0X0B 11 The UMC object is already

locked.

SL_COMMERR 0X0C 12 Transmission/Communication

error.

SL_NOTIMPL 0X10 16 Returned if a not implemented

method is invoked.

SL_CHANGEPSWDISABLE 0X19 25 The user cannot change the

password.

SL_USERUNKNOWN 0X20 32 The user is not present in the

system.

SL_USERNEVEREXPIRE 0X21 33 The user never expires.

SL_TICKETEXPIRED 0X22 34 The authentication ticket is

expired.

SL_USER_EXPIRED 0x27 39 The user is expired.

SL_PSWMINLEN_ERR 0x120 288 The account policy related to the

minimal password length has
been violated.

SL_PSW_CHANGE_FAIL 0X154 340 Password change failure.

SL_INVALID_NONCE 0x166 358 Login failed: invalid token. This

event may occur if you try to
access the login page directly
from the URL or if you leave the
login page open.

SL_WEAK_AUTH 0x167 359 Login failed: access not allowed

using weak authentication
method.

CRUD Operation Errors

Name Hexadecimal Decimal Description

Value Value

SL_ALREADYEXIST 0x0D 13 The UMC object already

exists.

SL_LOCK_NEEDED 0x23 35 A lock is needed to complete

the operation.

SL_NOT_LOCKED 0x24 36 The UMC object is not locked

so you cannot unlock it.

User Management Component 1.9 - UMC Service Layer API Developer Manual
47
A5E39179405-AC
7 UMC APIs Error Codes
6.5 Delete Roles

Name Hexadecimal Decimal Description

Value Value

SL_OBJVERMISMATCH 0X31 49 A UMC object has been

simultaneously modified by
two Web UI instances and an
object version mismatch has
been detected.

SL_INVALID_OPERATION 0x103 259 The operation cannot be

performed on the selected
object.

SL_OBJ_DOES_NOT_EXIST 0x111 273 The UMC object does not

exist or has not yet been
saved into the UMC
database.

SL_OBJECT_LOCKED_IN_DATABASE 0X153 339 The UMC object is already

locked.

SL_FAIL_NOTAMASTER 0x160 352 An attempt has been made to

modify the UMC database on
a machine that is not a
master.

SL_FAIL_BINDING_ADMIN_ROLE 0x161 353 An attempt has been made to

assign the Administrator role
to a group or the user who
performed the association,
either a UMX user or a Web
UI user, does not have the
Administrator role.

SL_OBJ_OFFLINE 0x0F 15 The user/group for which you

want to perform an operation
is offline and the operation is
not allowed for offline objects.

SL_INVALID_NAME_FOR_OFFLINE_OBJ 0x165 357 The offline user/group that

you are creating does not
follow the pattern
<domainName>\<objName>.

SL_INVALID_SID 0x5C 92 Invalid User Security

Identifier (SID). See Microsoft
Documentation on Security
Identifiers for more details.

User Management Component 1.9 - UMC Service Layer API Developer Manual
48
A5E39179405-AC
 7 UMC APIs Error Codes
6.5 Delete Roles

Provider Operation Errors

Name Hexadecimal Decimal Description

Value Value

SL_INVALID_PROVIDER 0x100 256 Operation not provided by this

provider.

SL_INVALID_HANDLE 0x101 257 An invalid handle was passed as

parameter.

SL_ERROR_LOADING_PROVIDER 0x102 258 An error occurred when loading

the provider.

Internal or Parameter Errors

Name Hexadecimal Decimal Description

Value Value

SL_INVALID_PARAMETERS 0x104 261 The method has an incorrect

parameter.

SL_MEMORY_ERROR 0x105 262 Memory allocation error.

SL_INITIALIZATION_ERROR 0x106 263 Initialization error.

SL_INVALID_LOCK_OPTION 0x108 264 The lock option has not been defined.

SL_INVALID_PROPERTY 0x109 265 The property has not been defined for
the object.

File Errors

Name Hexadecimal Value Decimal Value Description

SL_ACCESS_FILE_ERROR 0x112 274 Access file error.

SL_UNKNOWN_FILE_FORMAT 0x113 275 Unknown file format.

SL_FILE_NOT_FOUND 0x50 80 File not found.

SL_PATH_NOT_FOUND 0x51 81 Path not found.

SL_FILE_CREATION_FAIL 0x52 82 Error during file creation.

SL_PATH_CREATION_FAIL 0x53 83 Error during path creation.

SL_INVALID_PATH 0x54 84 Invalid path.

User Management Component 1.9 - UMC Service Layer API Developer Manual
49
A5E39179405-AC
7 UMC APIs Error Codes
6.5 Delete Roles

Function Rights Errors

Name Hexadecimal Decimal Description

Value Value

SL_RESOURCE_NOT_FOUND 0x150 336 The user does not have the correct
function right to perform the
requested operation. This error has
the same meaning as the
SL_MISSING_FUNCTION_RIGHT
error.

SL_INVALID_RESOURCE 0x151 337 The function right does not exist.

SL_MISSING_FUNCTION_RIGHT 0x152 338 The user does not have the correct
function right to perform the
requested operation. This error has
the same meaning as the
SL_RESOURCE_NOT_FOUND
error.

Service Layer Errors

Name Hexadecimal Value Decimal Value Description

SL_CLAIM_EXPIRED 0X155 341 The claim is expired.

SL_CLAIM_INVALID 0X156 342 The claim is invalid.

SL_JSON_ERROR 0X157 343 The .json file is not well formed.

SL_MKTKT_FAILURE 0X158 344 The "make ticket" operation failed.

SL_ABORTED 0x159 345 Operation aborted.

Package Errors

Name Hexadecimal Decimal Description

Value Value

SL_PACKAGE_CREATION_FAIL 0x55 85 Package creation failed.

SL_PACKAGE_COMPRESSION_FAIL 0x56 86 Package compression

failed.

SL_PACKAGE_UNCOMPRESSION_FAIL 0x57 87 Package decompression

failed.

SL_PACKAGE_ENCRYPTION_FAIL 0x58 88 Package encryption

failed.

SL_PACKAGE_DECRYPTION_FAIL 0x59 89 Package decryption

failed.

User Management Component 1.9 - UMC Service Layer API Developer Manual
50
A5E39179405-AC
 7 UMC APIs Error Codes
6.5 Delete Roles

Name Hexadecimal Decimal Description

Value Value

SL_PACKAGE_RESTORE_FAIL 0x5A 90 Package restore failed.

SL_PACKAGE_WRONG_PASSWORD 0x5B 91 Wrong password for the

package.

Database Errors

Name Hexadecimal Decimal Description

Value Value

SL_DBFILE_ACCESS_DENIED 0X32 50 The user cannot access a UMC

database file.

SL_DBFILE_ERROR 0X33 51 Generic UMC database file error.

SL_DBFILE_OUT_OF_SPACE 0X34 52 A UMC database file is full.

SL_ROLEIDS_OUT_OF_SPACE 0X35 53 No more role IDs are available in the

role database file. A purge of the roles
is needed.

User Alias Errors

Name Hexadecimal Decimal Description

Value Value

SL_INVALID_USER_ALIAS 0x5E 94 Invalid user alias name.

SL_USER_ALIAS_ALREADY_EXIST 0x5F 95 User alias already exists.

SL_BAD_PKI_FILTER_NAME 0x115 277 Invalid filter name or filter name

not present when authmode =
SL_PKI_FILTER_MASK.

Secure Application Data Support (SADS) Errors

Name Hexadecimal Decimal Description

Value Value

SL_INVALID_DOMAIN_NAME 0x60 96 Invalid domain name.

SL_NOT_CURRENT_DOMAIN 0x61 97 Input domain name is not the

current domain.

SL_INVALID_KEY 0x70 112 Invalid key.

SL_KEY_GENERATION_FAIL 0x71 113 Error during key generation.

SL_KEY_ENCRYPTION_FAIL 0x72 114 Error during key encryption.

User Management Component 1.9 - UMC Service Layer API Developer Manual
51
A5E39179405-AC
7 UMC APIs Error Codes
6.5 Delete Roles

Name Hexadecimal Decimal Description

Value Value

SL_KEY_DECRYPTION_FAIL 0x73 115 Error during key decryption.

SL_KEY_NOT_FOUND 0x74 116 Key not found.

SL_KEY_ENCRYPTION_NOT_ENABLED 0x75 117 Application key protection

(global policies) not enabled.

SL_MAX_NUM_KEY 0x76 118 The maximum number of

allowed keys has been
reached.

SL_KEY_DECRYPTION_NO_ID_FOUND 0x77 119 No SUID of the identity has

been found in EAK array.

SL_SADS_VERSION_ERROR 0x78 120 Wrong SADS version.

SL_WRONG_IDENTITY 0x79 121 Ticket authentication error

while decrypting a key.

SL_EAK_BAD_FORMAT 0x80 128 Bad format of the encryption

application object.

SL_SUBJECT_NOT_ENABLED 0x81 129 Encryption not enabled for the

specified subject.

SL_SUBJECT_KEY_OBSOLETE 0x82 130 The decryption has been

executed using an obsolete
key.

User Management Component 1.9 - UMC Service Layer API Developer Manual
52
A5E39179405-AC