Search
×
FR

Placeholder headline

This is just a placeholder headline

API Technical Report TDB-6 Chapter 6 – Density

$

204

BUY NOW

Placeholder headline

This is just a placeholder headline

API STD 560: Fired Heaters for General Refinery Services

$

721

BUY NOW

Placeholder headline

This is just a placeholder headline

API STD 64: Diverter Equipment Systems

$

324

BUY NOW

Placeholder headline

This is just a placeholder headline

API MPMS CH 17.10.1: Refrigerated Light Hydrocarbon Fluids – Measurement of Cargoes on Board LNG Carries

$

417

BUY NOW

Placeholder headline

This is just a placeholder headline

API RP 13B-1: Testing Water-based Drilling Fluids

$

418

BUY NOW

Placeholder headline

This is just a placeholder headline

API Technical Report TDB-12 Chapter 12 – Thermal Conductivity

$

214

BUY NOW

Placeholder headline

This is just a placeholder headline

API 16FI Frac Iron Guidelines and Requirements

$

129

BUY NOW

ISO 26136:2024

ISO 26136:2024 Information technology – OpenID connect – OpenID connect front-channel logout 1.0

CDN $115.00

SKU: 8dbdc0725818 Category:

Description

OpenID Connect 1.0 is a simple identity layer on top of the OAuth 2.0 protocol. It enables Clients to verify the identity of the End-User based on the authentication performed by an Authorization Server, as well as to obtain basic profile information about the End-User in an interoperable and REST-like manner.

This document defines a logout mechanism that uses front-channel communication via the User Agent between the OP and RPs being logged out that does not need an OpenID Provider iframe on Relying Party pages. Other protocols have used HTTP GETs to RP URLs that clear login state to achieve this. This document does the same thing. 

Edition

1

Published Date

2024-10-01

Status

PUBLISHED

Pages

10

Language Detail Icon

English

Format Secure Icon

Secure PDF

Abstract

OpenID Connect 1.0 is a simple identity layer on top of the OAuth 2.0 protocol. It enables Clients to verify the identity of the End-User based on the authentication performed by an Authorization Server, as well as to obtain basic profile information about the End-User in an interoperable and REST-like manner.

This document defines a logout mechanism that uses front-channel communication via the User Agent between the OP and RPs being logged out that does not need an OpenID Provider iframe on Relying Party pages. Other protocols have used HTTP GETs to RP URLs that clear login state to achieve this. This document does the same thing. 

Previous Editions

Can’t find what you are looking for?

Please contact us at: