Oidc User Auth Tab
In VoLTE Node testing, Select for UE authentication for Mission Critical Push-to-Talk (MCPTT) as specified in the 3GPP TS 23.280, 22.179, 23.179, 24.379, 24.380, 33.179, 24.382, 24.384 specifications, OpenID Connect 1.0, and IETF RFC 6749 (OAuth 2.0).
Available in IP Application Node, MME Nodal, PGW Nodal, SGW Nodal and Network Host (server DMF only) test cases when Enable Supplementary on the VoLTE tab is selected. Enables the OIDC User Auth Tab under the Gm Interface.
OAuth is a widely-used authorization framework based on HTTP. It allows applications to access resources on other servers in a secure and efficient way, without passing credentials from the resource owner to the third-party applications directly. Instead, it obtains tokens from the resource owner, and using the tokens to access the protected resource for a specific scope, lifetime, and with other access restrictions.
OpenId Connect ((http://openid.net/connect/faq)) is a thin layer built upon OAuth 2.0 to enhance the flows to perform authentication properly.
| Message Flow |
| Remote Auth Address |
Enter a valid IP address of the Remote Authorization server.
Tcl Parameter: OAuthRemoteAddr |
|
| Timeout (s) |
Enter the maximum time to wait for a response from the Auth server. Range: 1 to 65535 Default: 5
Tcl Parameter: OAuthTimeout |
|
| Message Flow |
See Data Message Flow (Data Traffic Tab > Data Message Flows) to create OIDC User Auth DMFs. Data Protocol = oidc.
[Basic] library has number of pre-configured DMFs for OIDC User Auth Client: - MCPTT_UE_OIDC_auth_client_http - MCPTT_UE_OIDC_auth_client_https
Network Host as IdM Server:
A number of pre-configured DMFs are added to the [Basic] library: - MCPTT_UE_OIDC_auth_server_http - MCPTT_UE_OIDC_auth_server_https
|
