Skip to content

Latest commit

 

History

History
84 lines (41 loc) · 2.64 KB

logout-uri-rules-789c752.md

File metadata and controls

84 lines (41 loc) · 2.64 KB

Logout URI Rules

Rules for the front and back-channel URIs.

Identity Authentication triggers a logout request to the front or back-channel URI.

The front and back-channel logout URI must be in the following format:

protocol://domain<:port>/<path><?query parameters>

For example: https://example.com:70/logout?abc=123.

When you construct the front and back-channel URIs, have the following in mind:

The length is limited to 499 characters.

  • Protocols - Use the HTTPS protocol. The HTTP protocol is only allowed for localhost.

    Example:

    https://example.com/logout

  • Localhost - It's allowed in the domain part.

    Example:

    http://localhost/logout

    https://localhost/logout

  • Wildcard - It's allowed in the domain part. Wildcards are only supported in front-channel flows. Although there's no restriction on using wildcards with single tenant apps, the use of wildcards was developed with multitenant applications in mind.

    Example:

    https://*.example.com/logout

    Allow during authorize call to register a URI with parameter logout_uri, for example: https://app1.example.com/logout.

  • IP Addresses - Usage of IP addresses isn't allowed.

Ports (optional)

After the domain part, you can put the port numbers. Always use a leading colon (:).

Example:

https://example.com:8080/logout

Restriction:

Usage of fragment identifier (#) isn't allowed. For example, you can't use https://example.com/path#index.html.

Related Information

Redirect URIs, Post Logout Redirect URI Rules

Token Policy Configuration for Applications

Configure Grant Types

OpenID Connect Front-Channel Logout 1.0 Specification

OpenID Connect Back-Channel Logout 1.0 Specification