');}.md-tag.md-tag--api{--md-tag-icon:url('data:image/svg+xml;charset=utf-8,');}.md-tag.md-tag--internal{--md-tag-icon:url('data:image/svg+xml;charset=utf-8,');}.md-tag.md-tag--public{--md-tag-icon:url('data:image/svg+xml;charset=utf-8,');}.md-tag.md-tag--product-weather{--md-tag-icon:url('data:image/svg+xml;charset=utf-8,');} The chat responses are generated using Generative AI technology for intuitive search and may not be entirely accurate. They are not intended as professional advice. For full details, including our use rights, privacy practices and potential export control restrictions, please refer to our Generative AI Service Terms of Use and Generative AI Service Privacy Information. As this is a test version, please let us know if something irritating comes up. Like you get recommended a chocolate fudge ice cream instead of an energy managing application. If that occurs, please use the feedback button in our contact form!
Insights Hub drives smart manufacturing through the industrial Internet of Things. Gain actionable insights with asset and operational data and improve your processes.
Creating MindsphereCredentials using App Specific Service Credentials¶
The app specific service credentials are obtained from Developer Cockpit or Operator Cockpit. During the development of an application you may provide the service credentials programmatically. The final application should obtain the client ID, client secret, app name and app version from the environment variables and the host tenant and user tenant from the user token as shown below.
The host tenant and user tenant values should not be hard-coded in the application as they are subject to change. MindSphereCredentials objects can extract these values from the user token provided as authorization parameter.
Creating MindsphereCredentials using Tenant Specific Service Credentials¶