Home > OpenID Connect OAuth Server by DnC

OAuth Server by DnC (OAuthSD) is an authentication server that implements OAuth 2.0 et OpenID Connect.

Secure data access with OpenID Connect

With the Single Sign On (SSO), an entity allows users of its applications to seamlessly navigate from one to the other. But even more:

By centralizing the authentication of applications and users, an OpenID Connect server makes it possible to perfectly control access to sensitive information.

In practice : "Authorization Code Grant"

When an application needs to authenticate user (for example to access protected resources), it will contact the OpenID Connect server. The latter identifies the application by exchanging with it an authorization code.
The server identifies the user of the application and determines its rights on this application. The user gives his consent to authorize the application to use all or part of his personal data.

This results in an authentication, binding the user and his personal data, the application and the rights of the user on the application (or vice versa) into a tamper-proof and transmissible object called Identity Token ( IDToken ).

The application then uses the Identity Token to access protected resources and obtain or modify data based on the rights of the user.

Different flows for different configurations

All application, server, and resource configurations do not provide the same level of security, especially for authenticating the application.

For optimal security, the application should be of "web" type and implement the Authorization Code Grant.

However, OpenID Connect can meet different needs, especially for mobile applications, with different Grant Types.

Supervision: organizing the configuration of the rights

In a large entity, with several thousand end-users (both staff and customers) and a large number of applications, it will not be possible to centralize the management of individual rights in relation to applications because they will be distributed users and applications among members of the entity.
A specific application will have to delegate the configuration of rights to the local level. Such an application is not part of the OpenID Connect specification. OAuthSD offers external applications the means to manipulate the data of the server through a HTTP API REST + TreeQL whose access is secured with ... OAuthSD.

Using an existing identification system: LDAP etc.

An organization implementing an identification system already has the means to manage users and their profile. OAuthSD allows the integration of third-party identification systems, whether standard such as LADP and Active Directory (Kerberos) or organization-specific (ID card, biometric identification ...).

In this case, the HTTP REST API makes it possible to automatically integrate this data by the authentication server. The result is a configuration in which the authentication server delegates the user’s identification to an Identity Provider.

The OpenID Foundation: standardization and certification

The OpenID Connect standard is coordinated by the largest IT companies within the OpenID Foundation. An abundant documentation provides the technical framework for the development of an authentication server (called "OpenID Connect Provider" or OP).
A battery of tests, made available by the foundation, allows the OAuthSD server to obtain the OpenID Connect Certification. This ensures that the authentication server conforms to the current state of the standard. A server should be updated and regularly tested.

What implications for client applications?

"Client" applications must be able to delegate user authentication to the OIDC server. More and more applications offer this possibility in accordance with the OpenID Connect standard.
When this is not the case, a special development is needed to adapt the application. This usually involves substituting an OIDC module for the code of the classical connection. Adaptation is therefore particularly easy in the context of a new development or an "open source" application.

DnC supports you

DnC supports you in your OpenID Connect project to implement your own OAuthSD authentication server.

DnC is an independent company whose policy is never to use or communicate the data collected. By entrusting us with the installation of your own authentication server, you can rest assured that your customers’ browsing will not be exploited for adverse advertising purposes. You can also avail yourself of a policy of protection of their personal data.

Latest articles :

Verifying the origin of the request received by a resource server


The transmission of tokens to protected resources implies that the latters are receptive to tokens of any origin. This presents an opportunity for an attacker (a foreign application) to exploit a compromised or stolen token.
Once more, the analysis reveals that we are only able to ensure data security in the case of the "Authorization Code" flow.
Consideration about the security of token transmission to resource servers (RS)
The proposed RFC 6749 standard is quite clear on the need to (...)


Definition of scopes and generalities on their use by applications


The extent of the authorization is defined by the Scopes. This is probably the most open point of the standard and therefore a difficult concept to master for the developer of an application using OpenID Connect.
The ability to modulate authorization extent based on the client application and the end user is an exceptionally interesting feature of OAuthSD.
We often see in OIDC a simple SSO, but it misses all the power of the device: the JWT identity token combines inseparably and in a (...)


OpenID Connect : Grant Type flows


The Grant Type flows specifically defined for the OpenID Connect protocol are:
Authorization Code Grant,
Implicit Grant,
Hybrid Flow.
See also: OpenID Connect : Summary of all authorization flows.
Authorization Code Flow (spec. : Authorisation code flow) - the most commonly used stream for traditional web applications as well as native / mobile applications ( with security concerns ). Involves an initial redirection of the browser to the authentication server for authentication and (...)


| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 |

Site Map :