Credentials

The Credentials module: registering a platform with the MOBI.Hub, renewing credentials and the Credentials object the hub sends.

Technical considerations

MOBI.Hub acts as the Sender for the Credentials module.

Whenever a CPO or EMSP intends to register a platform in the MOBI.Hub Interoperability Hub, the participant shall provide MOBI.Hub with CREDENTIALS_TOKEN_A.

Registration

The OCPI registration process within MOBI.Hub shall fail if:

• the entity does not support a compatible OCPI version (currently OCPI 2.2 or OCPI 2.2.1);
• the entity does not expose the required endpoints through the Versions and Version Details modules.

Updates and renewal

The following operations shall be supported by all systems:

• changing endpoints for an existing OCPI version;
• updating credentials and renewing credentials tokens.

Any party shall be able to initiate any of the above operations.

MOBI.Hub may periodically trigger credential renewal procedures with connected systems. The frequency and renewal policies are implementation-specific and may evolve over time.

Operator details

All operator information, including logos and business details, shall be provided through the business_details field. It is the participant's responsibility to keep this information up to date.

MOBI.Hub Credentials object

The Credentials object sent by the MOBI.Hub shall contain:

• role: HUB
• country_code: PT
• party_id: HUB

The Credentials endpoint shall be advertised with the RECEIVER role.

Multiple platforms and entities

For a given participant, different OCPI modules may be implemented by different technical platforms, provided that there is no functional overlap between them. Additionally, a single technical platform may represent multiple entities within the MOBI.Hub ecosystem.

URL fields shall comply with the requirements defined by the OCPI specification and must be accessible through HTTPS.