Production and pre-production
Client registration is a manual process performed in collaboration with an account manager of Cleverbase. As input, the redirection URI(s) and client name (for displaying purposes) of the client is required. Client registration will lead to a confidential OAuth 2.0 Client (RFC 6749) with two parameters:
| Parameter | Classification |
|---|---|
| OAuth 2.0 Client Identifier | Public Information |
| OAuth 2.0 Client Secret | Private information |
This OAuth 2.0 Client can subsequently act as a client to the Cleverbase Identification and Signing APIs.
Development and test
The Identification service stub and the Signing service stub need no registration. Any client implementation can use the shared test clients below; both work on both stubs, and any redirection URI is allowed.
| Test client | Client ID | Client Secret | Signing service stub | Identification service stub |
|---|---|---|---|---|
| RSA-2048 | 6dd5f48d-bcd9-4a98-8a4c-5c82182f5be4 | 11628999-cb61-4c62-8e1f-09699dcb5521 | one RSA-2048 credential | the stub user |
| P-256 | 5ee4ad61-e6f4-4541-9efc-534dae34a1b8 | bb60145b-e95a-4431-bdf1-23df33c23be7 | one ECDSA P-256 credential | the same stub user |
On the Signing service stub the client you authenticate with decides the key type, so run your flow once with each client to test both. See Change notice: ECDSA P-256 signing keys, section 6.1. If you only use the Identification service stub, either client will do.
These clients only exist on the stubs. For acceptance and production you register your own client, as described above.