Basic Authentication flow¶
If there is a necessary integration that can not use any of the above authentication flows, the last option is for a client to use HTTP Basic authentication in order to access the system. This by default is disabled on the IFS proxy due to security concerns and has to be specifically enabled using BASIC_AUTH parameter in custom values yaml, which is not usually recommended.
This option is only available for IFS Cloud Remote Deployments.
In this flow, the client application does not need to call the token endpoint. Instead of that when calling the relevant IFS cloud API the Authorization header should be set in the request headers.
Authorization: Should be set to “Basic
Sample IFS cloud API request with basic authentication