All services require a valid token from the IdP when called.

All services require TLS (version 1.2 or higher) for transport security.

In line with industry best practices the HIMSA IdP does not allow IFRAME based usage for any kind of user interactive authentication. An X-FRAME-OPTIONS HTTP header is always returned with the value ‘SameOrigin’.

...

Noah ES contains an Identity Provider that supports OAuth 2.0 and OpenId Connect. The Identity Provider (IdP) is used for Authentication.All services

require a valid token from the IdP when calledThe flow below applies to user interactive apps. For service apps / machine-to-machine client type the simplified Client Credentials flow is used.

1. Request

Parameters that must be supplied:

• URI and port number

  • QA environment: idp.qa.eu.noah-es.com:443

  • EU Production: idp.eu.noah-es.com:443

  • US Production: idp.us.noah-es.com:443

• ClientId: Supplied by HIMSA

• Client secret: Supplied by HIMSA if required

• Scope: openid profile noah.cloud.app.api

  • If relevant for your app and app registration allows: offline_access

• Flow: Authorization Code + PKCE

• RedirectURI: IdP will redirect the client to this after successful authentication, with tokens for accessing the API. You must inform HIMSA about this, because we need to whitelist it

• Extra options

  • culture-lcid: Culture LCID code for localizing the website

...

Note: This is done automatically if you are using HIMSA's .NET Client.

Only if relevant for your app and if app registration allowsWe never issue refresh tokens for service apps / machine-to-machine apps.

Lifetime of access tokens and refresh tokens varies depending on the client type and app type.

Logging off

In case a user only set up 1 account and that account is of type single sign-on, logging off will redirect the user directly to the login page. In that case it will not be possible to set up a different account.

...