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
  • Onboard an existing application
  • User Context
  • Application Identification

Authentication

PreviousDesign GuidanceNextAccessing data exposed by the platform

Last updated 2 years ago

Onboard an existing application

Onboarding an existing application that does not require data context from its users or the platform does not require additional authentication beyond application credentials passed through Eureka or the Pre-defined Sidecar. To utilise collected AAS & Submodel data, further configuration is required.

User Context

The IndustryApps platform allows hosted applications to interact with users through a user management and permission system, which is available through the dedicated platform-api.js API that can be integrated into your application.

An authentication token unique to a user is required to utilise AAS & Submodel data collected by users. Additional information can be found in .

The API requires the application to be interacted on the platform. Outside of the platform scope, application authentication is automatically denied. Thus, our dedicated team provides a demo customer portal for testing purposes once the application has been onboarded to the platform.

Application Identification

To utilise data integration exposed by the platform, the application is required to post a request for an access token to a dedicated endpoint. The access token expires 30 seconds after each response by the endpoint.

Each request to the platform endpoints requires both an application access token and a user token available by the user management and permission API. Additional information can be found in .

Accessing data exposed by the platform
Data Integration