Skip to content

Via RND

Request access ​

RND reviews every access request while the bus is in early testing.

1. Send the request Available now ​

Use the Request access form on the home page. Choose A vendor, say what you'll test and tick the message families you expect to produce or consume. You get a reference such as REQ-1A2B3C4D.

2. RND reviews it Via RND ​

An RND engineer reviews the request in the portal and approves or declines it. Either way, the decision comes to you by email, with the reason if it's declined. On approval RND creates your organisation and its first workspace, and you get a portal sign-in: a temporary password by email, then your own password and an authenticator app. Multi-factor sign-in is required. When you sign in, accept the invitation to your workspace; it expires after 14 days. See Your workspace in the portal.

3. Set up your apps yourself Available now ​

There's nothing else to send RND. Once you're in your workspace, you do the rest in the portal:

  • create your apps and connect producers with the system_ids and message types they send (Credentials);
  • choose how each one signs in: a client secret, an AWS role or your own identity provider (Authenticate);
  • create consumer connections with the message types they receive, and read them over HTTPS (Consumer connections).

Plan what you'll set up with Which parts apply to you and Plan your integration. The whole flow, step by step: Integrate as a vendor.

Once you're in, invite your colleagues yourself from the Team page: see Your team. The AWS IAM role that reads a consumer queue directly is yours to register too, on the connection (Read with AWS credentials).

How long your request is kept Available now ​

  • Your request, with the details you sent in the form, is deleted 12 months after you make it.
  • The IP address it was sent from is removed as soon as RND approves or rejects it.
  • To have it deleted sooner, ask RND and quote your reference (from the portal, use Ask RND). An RND admin deletes the request in the portal, and the audit log keeps only that it was deleted, and by whom.

Deleting a request doesn't touch the organisation and workspace an approval created.

SOM is an open standard maintained by the SOM working group. This service is not endorsed by it.