![\"\"](\"https:\/\/docs.iotconnect.io\/partnerprogram\/wp-content\/uploads\/2021\/04\/ids-01.jpg\")
<\/p>\nTypically, each application layer (front-end, middle-tier and back-end) resource must be protected by implementing authentication and\/or authorization \u2013 often against the same user store. Outsourcing these fundamental security functions to a security token service prevents duplicating this functionality across all applications and endpoints.<\/p>\n
Restructuring the application to support a security token service leads to the following architecture and protocols:<\/p>\n
<\/p>\n
Authentication is needed when an application needs to verify the identity of the current user. Usually, applications manage user data and makes sure that the user data is accessible to an authenticated user only. The most common examples are (classic) web applications \u2013 but native and JS-based applications also have a need for authentication.<\/p>\n
The most used authentication protocols are SAML2p, WS-Federation and OpenID Connect \u2013 SAML2p being the most popular and the most widely deployed.<\/p>\n
OpenID Connect is the newest of the three but it is getting wide popularity since it has the potential to cater modern application needs. It was built for mobile application scenarios right from the start and is designed to be API friendly.<\/p>\n
Identity Server (IDS) is the middleware that adds the spec compliant OpenID Connect and OAuth 2.0 endpoints to an arbitrary application.<\/p>\n
Typically, you build (or re-use) an application that contains a login and logout page (and maybe consent – depending on your needs), and the Identity Server middleware adds the necessary protocol heads to it so the client applications can talk to it using those standard protocols.<\/p>\n
Below is the architecture diagram that explains how default\/external Identity provider(s) (IDP) redirects to \/IOTCONNECT\u2122 or external IDP login system using \/IOTCONNECT\u2122 Identity Server.<\/p>\n
![\"\"](\"https:\/\/docs.iotconnect.io\/partnerprogram\/wp-content\/uploads\/2021\/04\/ids-02.jpg\")
<\/p>\n
The \/IOTCONNECT\u2122 platform supports authentication with default IDP as well as external IDP. Once the company user initiates login from the \/IOTCONNECT\u2122 portal, it first redirects to the Identity server (login.iotconnect.io) and verify initial company configuration(s). Finally, the System redirects the user to the \/IOTCONNECT\u2122 default login page or external IDP login page based on company configuration.<\/p>\n
\/IOTCONNECT\u2122 IDS stores below-mentioned user information in the data store for both default and external IDP.<\/p>\n
Custom authentication flow will help companies that do not have any existing user base on any third-party identity provider such as Azure AD, Auth0, Okta etc. It will allow \/IOTCONNECT\u2122 companies to store their user information in Identity server SQL database.<\/p>\n
![\"\"](\"https:\/\/docs.iotconnect.io\/partnerprogram\/wp-content\/uploads\/2021\/04\/ids-03.jpg\")
<\/p>\n
By default, the \/IOTCONNECT\u2122 platform provides custom IDP if the company has not defined any identity provider before creating the company in \/IOTCONNECT\u2122. <\/p>\n
External authentication flow can be useful when any registered company already has an existing user base available on external IDP and want to use the \/IOTCONNECT\u2122 platform. <\/p>\n
Companies that seek to integrate external IDP with \/IOTCONNECT\u2122, must follow certain steps on their account and provide the required information to \/IOTCONNECT\u2122. The overall high-level process to integrate external IDP with IDS is depicted below:<\/p>\n
![\"\"](\"https:\/\/docs.iotconnect.io\/partnerprogram\/wp-content\/uploads\/2021\/04\/ids-04.jpg\")
<\/p>\n
Let us see how a company can integrate external IDP with \/IOTCONNECT\u2122 IDS. We have taken Auth0 IDP as an example below. <\/p>\n
To integrate Auth0 with \/IOTCONNECT\u2122, a company needs to provide basic information from Auth0 Application to \/IOTCONNECT\u2122. The steps that the company needs to follow are as below:<\/p>\n
![\"\"](\"https:\/\/docs.iotconnect.io\/partnerprogram\/wp-content\/uploads\/2021\/04\/ids-05.jpg\")
<\/li>\n![\"\"](\"https:\/\/docs.iotconnect.io\/partnerprogram\/wp-content\/uploads\/2021\/04\/ids-06.jpg\")
<\/li>\n![\"\"](\"https:\/\/docs.iotconnect.io\/partnerprogram\/wp-content\/uploads\/2021\/04\/ids-07.png\")
<\/li>\n<\/ul>\n\/IOTCONNECT\u2122 offers two ways to support authentication for companies who want to build solutions on top of it. In this flow, the user will be redirected to either \/IOTCONNECT\u2122 IDS login page or external IDP login. IDS will decide based on logged in user with company configuration. To initiate Implicit Flow solution the company needs to have the following details to start integrating on their front-end portal (UI). There are different libraries available to integrate Implicit on UI framework. Your library needs to setup the URL given below once all setup is done from \/IOTCONNECT\u2122. At Present, Solution developer can provide redirect and logout redirect URL via Email or by creating a support ticket. Alternatively, one can contact \/IOTCONNECT\u2122 support team as well. Overview Typically, each application layer (front-end, middle-tier and back-end) resource must be protected by implementing authentication and\/or authorization \u2013 often against the same user store. Outsourcing these fundamental security functions to a security token service prevents duplicating this functionality across all applications and endpoints. Restructuring the application to support a security token service leads to […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":13612,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"template-page-full-width.php","meta":{"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0},"acf":[],"_links":{"self":[{"href":"https:\/\/docs.iotconnect.io\/partnerprogram\/wp-json\/wp\/v2\/pages\/13620"}],"collection":[{"href":"https:\/\/docs.iotconnect.io\/partnerprogram\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/docs.iotconnect.io\/partnerprogram\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/docs.iotconnect.io\/partnerprogram\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/docs.iotconnect.io\/partnerprogram\/wp-json\/wp\/v2\/comments?post=13620"}],"version-history":[{"count":3,"href":"https:\/\/docs.iotconnect.io\/partnerprogram\/wp-json\/wp\/v2\/pages\/13620\/revisions"}],"predecessor-version":[{"id":13772,"href":"https:\/\/docs.iotconnect.io\/partnerprogram\/wp-json\/wp\/v2\/pages\/13620\/revisions\/13772"}],"up":[{"embeddable":true,"href":"https:\/\/docs.iotconnect.io\/partnerprogram\/wp-json\/wp\/v2\/pages\/13612"}],"wp:attachment":[{"href":"https:\/\/docs.iotconnect.io\/partnerprogram\/wp-json\/wp\/v2\/media?parent=13620"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nUsing \/IOTCONNECT\u2122 Authentication API management.<\/strong>
\nCompanies can use \/IOTCONNECT\u2122 Consumer APIs management that a Solution developer uses typically to build their Solution on top of \/IOTCONNECT\u2122. Solutions can use Authenticate API module to authenticate their users. The solution key is mandatory to perform user authentication. The screenshot to illustrate the same is given below.<\/p>\n![\"\"](\"https:\/\/docs.iotconnect.io\/partnerprogram\/wp-content\/uploads\/2021\/04\/ids-08.png\")
<\/p>\nImplicit Flow \/ Redirection Flow<\/h3>\n
\nAuthority URL:<\/strong> https:\/\/login.iotconnect.io<\/a>
\nClientID:<\/strong> iotconnect
\nRedirect URL:<\/strong> https:\/\/yoursolutiondomain.com\/callback<\/a>
\nLogout Redirect URL:<\/strong> https:\/\/yoursolutiondomain.com<\/a>
\nResponse Type:<\/strong> “id_token token”
\nScope:<\/strong> “openid profile iotconnect.api.fullaccess”
\nacr_values:<\/strong> “solutionCode:YOUR_SOLUTION_GUID”<\/p>\n","protected":false},"excerpt":{"rendered":"