Changes for page ONEcount SAML Server -- How it works

Last modified by Admin User on 2025/01/16 14:24

From 2.1 to 1.1 From 5.1 to 4.1

From version 4.1

edited by Admin
on 2020/01/18 13:45

Change comment: There is no comment for this version

To version 2.1

edited by Admin
on 2020/01/18 13:43

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)
Objects (1 modified, 0 added, 0 removed)
- Confluence.Code.ConfluencePageClass[0]

Details

Page properties

Title

@@ -1,1 +1,1 @@
--SSO Server: ONEcount SAML Server
++SAML Setup

Content

@@ -1,204 +1,0 @@
--
--
--{{id name="_GoBack"/}}
--SAML is setup on ONECount which can support both IDP and SP initiated logins. The main use of this saml is to provide authentication and authorization services for the SP while ONECount being IDP. We are using OPENSAML API to read the login requests and create SAML responses based on the authentication result. This document uses the following abbreviations.
--SP (Service Provider) : The system which is having the services the user requests for. The Service provider would just render services based on the authentication information provided by IDP.
--IDP (Identity Provider) : The system which manages the user details and the user privileges. The IDP would authenticate user and provide necessary information regarding the user to the SP.
--SAML: Security Assertion Markup Language is an XML-based, open-standard data format for exchanging authentication and authorization data between an identity provider and a service provider. SAML is a product of the OASIS Security Services Technical Committee. This defines the way SP and IDP communication protocols and how to react to requests.
--**SSO SERVICES:** In our ONECount we primarily use SAML for SSO Services across all the domains. The SSO services can be broadly divided into 2 types they are
--
--* SP Initiated login
--* IDP Initiated Login
--
--**SP Initiated login:** In this type of login the service provider requests for authentication to the IDP on for the same site. In our setup the example for this is harbourside MEDED website login. In SP initiated login the SP needs to create SAML request and send into to ONECount. The onecount then authenticates the user and sends the required details to the SP back as SAML response.
--**IDP Initiated login:** In this type of login the request for authentication would be by made by a partner site or third party site other than SP. In our setup the example is for ethos where the harbourside acts as partner site and has link to ethos websites where we authenticate the user and send required information to SP which is ETHOS in this context. In this type login is initiated by IDP to the SP.
--**DataBase models:** we have 2 tables in onecount_super data base as these configurations are common for all the clients. WE populate these tables based on the saml meta data file of service provider and other configurations. The table names are
--
--{{id name="OLE_LINK2"/}}
--
--{{id name="OLE_LINK3"/}} onecount_saml_metadata and
--
--{{id name="OLE_LINK4"/}}
--
--{{id name="OLE_LINK5"/}}
--
--{{id name="OLE_LINK6"/}} onecount_saml_relaystate_mapping and their structure is as follows.
--onecount_saml_metadata
--
--(% class="wrapped" %)
--|=(((
--**Column**
--)))|=(((
--**Type**
--)))|=(((
--**Comments**
--)))
--|(((
--entity_id
--)))|(((
--varchar(400)
--)))|(((
--(% class="content-wrapper" %)
--(((
--
--
--{{id name="OLE_LINK1"/}}The entity id of SP which we get in SAML Metadata file.
--)))
--)))
--|(((
--soap_binding
--)))|(((
--text
--)))|(((
-- The SOAP binding of SP which we get in SAML Metadata file.
--)))
--|(((
--redirect_binding
--)))|(((
--text
--)))|(((
-- The redirect binding of SP which we get in SAML Metadata file.
--)))
--|(((
--certificate_encryption
--)))|(((
--text
--)))|(((
-- The certificate encryption key of SP which we get in SAML Metadata file.
--)))
--|(((
--certificate_signature
--)))|(((
--text
--)))|(((
-- The certificate signature key of SP which we get in SAML Metadata file.
--)))
--|(((
--logout_post_binding
--)))|(((
--text
--)))|(((
-- The logout post binding of SP which we get in SAML Metadata file.
--)))
--|(((
--logout_redirect_binding
--)))|(((
--text
--)))|(((
-- The logout redirect binding of SP which we get in SAML Metadata file.
--)))
--|(((
--post_binding
--)))|(((
--text
--)))|(((
-- The post binding of SP which we get in SAML Metadata file.
--)))
--|(((
--expiry
--)))|(((
--date
--)))|(((
-- The expiry date of metadata of SP which we get in SAML Metadata file.
--)))
--|(((
--xml_dump
--)))|(((
--longtext
--)))|(((
-- The whole xml metadata as string.
--)))
--|(((
--saml_id
--)))|(((
--int(11)
--)))|(((
-- Unique primary for this table
--)))
--|(((
--fields
--)))|(((
--varchar(400)
--)))|(((
--JSON format string of demographic fields of user the SP needs with onecount question ID as key and name the SP wants for this particular question.
--Sample : {1:Email,226:Prefix,4:First name,218:Middle name,5:Last name,12:Postal code,98:Degree,234:Profession,242:Specialty,ocid:OCID}
--)))
--|(((
--client_auth
--)))|(((
--varchar(400)
--)))|(((
-- Client login URL to login page to which we send user for challenge questions when cookies are not found.
--)))
--|(((
--appkey
--)))|(((
--varchar(200)
--)))|(((
-- The app key for the client which we use to make requests to ONECount API.
--)))
--|(((
--brand_info
--)))|(((
--varchar(40)
--)))|(((
-- The brand information required for styling the login/lookup page.
--)))
--
--
--onecount_saml_relaystate_mapping
--
--(% class="wrapped" %)
--|=(((
--**Column**
--)))|=(((
--**Type**
--)))|=(((
--**Comments**
--)))
--|(((
--saml_relaystate_id
--)))|(((
--int(11)
--)))|(((
-- Unique primary key for this table
--)))
--|(((
--saml_id
--)))|(((
--int(11)
--)))|(((
--Foreign key from onecount_saml_mapping table
--)))
--|(((
--relaystate
--)))|(((
--varchar(400)
--)))|(((
--Relay state pattern or SP website address sample education.annenberg.net
--)))
--|(((
--client_id
--)))|(((
--int(11)
--)))|(((
-- Client id of our client
--)))
--
--
--\\\\\\\\\\\\\\\\\\\\When ever we need a new client to use the saml when we configure these parameters from the metadata file and the conf paramaters they provide they should be good.
--**Login Mechanism :** The total login process can be divided into 3 parts
--
--* Login Request
--* Authentication
--* Login Response
--
--Login Request: The login request needs to be a valid saml request.
--SP intitiated login: In the case of the SP initiated login ONECount supports Post request with the request payload. We read the request by opensaml java api and extract the required parameters for authentication.
--IDP Initiated login: In the case of IDP initiated login the partner site needs to have the relay state which is the url of the SP that they want to user to access. They also need to add a query parameter clientid which is used by the onecount to correctly identify the client- SP pair.
--Login Mechanism:
--The SAML Server relies on cookies for user identification. When the saml receives the login request that looks up the configuration form the database based on entity ID if its SP initiated or relay state and clientid. Then that checks for OCGT cookie. If the cookie is found then that searches the onecount_super database for the ocid of the user form OC_CLIENTS_TOKENS table based on the client id and ocgt value. If an entry is found that means that we are able to identify the user based on the oc_gt cookie.
--If the cookie is not found or the user could not be identified based on oc_gt and clientid then the server is unable to accurately identify the user then the saml redirects the user to login/lookup page for further authentication.while redirectiong the user the whole url of partner site is URLENCODED and sent as return parameter to login/lookup page. When the user authenticates himself the login server sets the updated cookie for the user which is taken and searched in the database.
--When the user is found the server makes a call to ONECount API to retrieve the user information. Once the user information is acquired the saml request is generated.
--SAML Response:
--The response is generated based on the configuration files using opensaml API. If that is SP initiated login then we have the extra parameter "InResponseTo" in the response which will have the unique request identifier which is used by the service provider to determine their internal state. In the request if the server receives any relay state then SAML server retains that and forwards the relay state without any modification. If it is IDP initiated login then the server will have the SP requested url as the relay state. In our setup we are using URL post binding to send the response to the SP.

Confluence.Code.ConfluencePageClass[0]

id

@@ -1,1 +1,1 @@
--23331755
++23331749

url

@@ -1,1 +1,1 @@
--https://info.onecount.net//wiki/spaces/OD/pages/23331755/SSO Server: ONEcount SAML Server
++https://info.onecount.net//wiki/spaces/OD/pages/23331749/SAML Setup