How to access protected Orange APIs resources using ‘2-legged’ OAuth (i.e. client_credentials grant type)
In the following resources we share best practices and technical information to integrate Orange APIs.
How to access protected Orange APIs resources using “3-legged” OAuth (i.e. authorization_code grant type)
In order to benefit from the SMS OTP Authentication and Consent, the Service Provider must provide the end-user’s mobile number in his API request. The mobile number must be encoded (see below) added to the request using the login_hint query_string parameter. Creating the login_hint for SMS OTP Authentication and Consent: The mobile number must be […]
Best practices for Orange API error handling and troubleshooting
In this document, we present a list of important security measures that need to be taken into account when implementing clients that integrate Orange APIs.
Retrouvez la documentation technique des réseaux Orange France pour vous aider à connecter votre objet IoT et développer vos services.
Mobile Connect is a user authentication and identity service based on the OpenID Connect/OAuth2 standards.
OAuth 2.0 defines a protocol for securing application access to protected resources, which are accessed through REST APIs. OAuth 2.0 relies on access tokens presented by client applications (on behalf of end-users or not) when requesting access to protected resources via APIs.
OpenID Connect 1.0 is a simple identity layer on top of the OAuth 2.0 protocol.
In this guide we explain the Orange France end-user account interfaces, so that you can understand your users experience, in particular with respect to Orange authentication and consent form.