2.3.2. Identity Manager enabler

2.3.2.1. Introduction 

Using OAuth2 protocol, it will offer a federated identification service where service requester and provider will be able to establish a trusted relation without previously knowing each other. This way a secure identification process is completed without the service provider having received the re-quester credentials.

2.3.2.2. Features 

Identity Management enabler will store user credentials and data. Using OAuth2 protocol, it will offer a federated identification service where service requester and provider will be able to establish a trusted relation without previously knowing each other.
When a requester asks for a service, the provider will redirect the request to a third-party identity server, known by both parties, so the requester can identify itself and obtain a session token. The service provider will ask the identity server to validate the token and provide data about the requester. This way a secure identification process is completed without the service provider having received the requester credentials.
Identity Manager enabler admin Contains the user or entities credentials store and data. It will offer a OpenId/OAuth2 interface.
Identity Manager enabler authentication Offers will offer a OpenId/OAuth2 interface and validates agains the locla or user db.
Local user db Contains the user or entities credentials store and data.

2.3.2.3. Place in architecture 

2.3.2.4. User guide 

The identification server will offer two interfaces, OAuth2 for identity management and a REstFull interface for server management.

The API for management has the following specification:

The OAuth2 interface is provided based on the standard.

2.3.2.5. Prerequisites 

The enabler is prepared to run in a K8S environment. The creation is prepared to be autonomous in such a working environment.

The service consumer will be required to communicate with the server using the standard OAuth2 interface.

2.3.2.6. Installation 

Enabler is provided as a Helm chart. Refer to specific deployment instructions.

2.3.2.7. Configuration options 

The IdM options for the rest API to connect are available in the libconfig.py file.

remote_address: str = "keycloak"
remote_port: str = "8080"
remote_username: str = "admin"
remote_password: str = "xxxx"
remote_realm: str = "master"
remote_https: str = "no"

kc_api_token_url_pre: str = "/auth/realms/"
kc_api_token_url_post: str = "/protocol/openid-connect/token"
kc_api_serverinfo_url: str = "/auth/admin/serverinfo"

2.3.2. Identity Manager enabler

2.3.2.1. Introduction 

2.3.2.2. Features 

2.3.2.3. Place in architecture 

2.3.2.4. User guide 

2.3.2.5. Prerequisites 

2.3.2.6. Installation 

2.3.2.7. Configuration options 

2.3.2.8. Developer guide 

2.3.2.9. Version control and release 

2.3.2.10. License 

2.3.2.11. Notice(dependencies)