...
Saga_json |
---|
"security": { "enable": true, "inactiveInterval": 600, "encryptionKeyFile" : "./bin/saga.ek", "defaultRole": "admin", "type": "saml", "saml": { "keystorePath": "config/samlKeystore.jks", "keystorePassword": "samlKeystore-passwd", "privateKeyPassword": "samlKeystore-passwd", "identityProviderMetadataPath": "config/identityProvider.xml", "serverURL": "https://your_server_url_here", "nameIdAttribute": "http://schemas.microsoft.com/identity/claims/identityprovider" } } |
...
Currently Saga Server has 3 methods to login, (besides the login of SAML)
...
The Form login , will enable the login page for the Saga Server, here you can user your username and password to access. This method uses a POST HTTP request.
When employing Basic Authentication, users include an encoded string in the Authorization header of each request they make. The string is used by the request’s recipient to verify user’s identity and rights to access a resource.
The Authorization header follows this format:
Authorization: Basic <credentials>
We then construct the credentials
like this:
Code Block |
---|
curl --location --request GET 'http://localhost:8080/saga/api/client/process/units' \ --header 'Authorization: Basic <Base64(USERNAME:PASSWORD)>' |
...
When employing API Keys, the service include an API Key string in the Authorization header of each request they make. The string is used by the request’s recipient to verify service’s identity and rights to access a resource.
The Authorization header follows this format:
Authorization: Saga <API_KEY>
...