Developer Documentation
  • Documentation Overview
  • Development Introduction
  • Getting Started
  • Fundamentals
    • Deploy an App via Pre-defined Sidecar
      • Sidecar Tutorial: Server-side
      • Sidecar Tutorial: Client-side
      • Sidecar Tutorial: Docker & Deploy
    • Deploy an App with Eureka
    • Design Guidance
  • Authentication
    • Accessing data exposed by the platform
    • Single Sign-On
      • Angular
      • Vue
      • Java Spring: Accepting JWT
      • Python Django: Accepting JWT
    • User and Role Identification
  • APIs | Data Integration
    • Submodel Index
    • Masterdata
    • Transactional data
  • Docker Information
    • Ruby Stack
    • Golang Stack
    • Node JS Stack
    • Java Spring Stack
    • Python Stack
  • Connect to the Platform
    • Integrate using Eureka Rest APIs
    • Use our Pre-built sidecar
    • Production deployment
  • Add-on Features
    • IApps-Navigation
  • Testing
  • FAQs | Troubleshooting
  • Registration
    • Application pre-requisites
      • Basic Requirements
    • Register Developer Account
    • Submit basic application info
    • Onboard Application
      • Submit Appstore details
        • App basic information
      • Configure Application
        • App Permission
        • App Data
        • AAS Instance
        • Licensing
        • Access Rights
        • Account Info
        • Terms Of Use
        • Pricing
      • Publish and test
        • Deploy
        • Register into Service Discovery
    • Publish to Marketplace
  • User Experience
  • The business model - How do I get paid?
  • References
    • IndustryApps - Intro
    • What is an Asset Administration Shell?
    • What is ECLASS?
      • How is ECLASS and Concept dictionary are used
    • Industry 4.0 standards
    • Customer Terms of Use
      • Subscription Order
    • Solution provider Terms of Use
      • Contract regions
      • Submission Form ( Solution provider)
Powered by GitBook
On this page
  • IndustryApps Single Sign-on (SSO)
  • IndustryApps SSO Model
  • SSO Example in your Third-party Application
  • Integrating SSO
  • Credentials
  • Optional
  1. Authentication

Single Sign-On

PreviousAccessing data exposed by the platformNextAngular

Last updated 2 years ago

Single Sign-on is currently being upgraded, additional features will continue to be implemented.

SSO Authentication, in collaboration with IndustryApps, allows users to access authorised only application resources by integrating IndustryApps login single sign-on into your application. The feature can be integrated as an addition to your externally hosted application's currently held single sign-on options.

IndustryApps Single Sign-on (SSO)

Once SSO is set up, third-party app users can sign into IndustryApps and access their resources without requiring an additional sign-in. SSO redirects to the IndustryApps login portal, requesting the users' credentials such as username and password, which gives users access to their authentication restricted resources.

Single Sign-on does not grant permissions for applications for Data Integration. To utilise , and please see .

IndustryApps SSO Model

SSO Example in your Third-party Application

Integrating SSO

The upcoming examples illustrates how SSO can be integrated within your applications' code with IndustryApps SSO in the following technologies.

Configure and Utilise Client-side Applications such as:

  • Angular

  • Vue

Accept JWT with Server-side Applications such as:

  • Java Spring 5

  • Python Django

Credentials

To utilize SSO the following credentials are required to be implemented in your application configuration:

  • Issuer

For Development purposes please utilise the UAT environment URI available below:

https://auth.uat.industryapps.net/auth/realms/IndustryApps

For Production, please utilise the environment URI available below:

https://auth.industryapps.net/auth/realms/IndustryApps
  • ClientID

Each Application which utilises Single Sign-on will be provided a dedicated ClientID during onboarding which acknowledges access.

  • Redirect URI

The application will require a redirect URI to navigate back after authentication has been completed. The structure of the URI should be implemented as seen below.

Development:

https://democustomer.uat.industryapps.net/<APPCODE>/

Deployment:

https://democustomer.industryapps.net/<APPCODE>/

Deployment will contain the environment URI of the platform customer portal instead of the demo-customer portal.

Optional

Client Secret

If your application is currently utilizing an identity and access management service provider which requires a client secret, use the client secret code available on your Platform Dashboard. By default it is not required.

Metadata URL

In cases such as an identity provider requiring a .well-known/openid-configuration URL please use the following credential:

For development purposes please utilise the UAT environment URI available below:

https://auth.uat.industryapps.net/auth/realms/IndustryApps/.well-known/openid-configuration

For deployment, please utilise the environment URI available below:

https://auth.industryapps.net/auth/realms/IndustryApps/.well-known/openid-configuration

Masterdata
Transactional data
Submodel data
Data Integration
SSO Model
Sign-in Options
Applications > My_APP > App Information