B.2 MCPTT client registration

33.1793GPPRelease 13Security of Mission Critical Push To Talk (MCPTT) over LTETS

Before an MCPTT client can obtain ID tokens and access tokens (required to access MCPTT resource servers) it shall first be registered with the IdM server of the service provider as required by OpenID Connect 1.0. The method by which this is done is not specified by this profile. For native MCPTT clients, the following information shall be registered:

– The client is issued a client identifier. The client identifier represents the client’s registration with the authorization server, and enables the IdM server to reference parameters associated with that client’s registration when being requested for an access token by the MCPTT client.

– Registration of the client’s redirect URIs.

Other information about the MCPTT client such as (for example): application name, website, description, logo image, legal terms to be consented to, may optionally be registered.