On the configuration file you can find the security section, in this section option like the encryptionKey, inactive timeout, roles and authentication can be found:
Change the encyptionKeyFile as soon as you start a working on a new project
$action.getHelper().renderConfluenceMacro("$codeS$body$codeE")
Saga Server counts with 3 authentication types
Config authentication is the most basic of all, ideal for demos, but not recommended for production environments, unless in a close environment. This authentication uses Users, Passwords and Roles defined in the same config file, under the users field, one entry per user.
Config will allow you to login via Form and Basic Authentication $action.getHelper().renderConfluenceMacro("$codeS$body$codeE")
LDAP, the Lightweight Directory Access Protocol, is a mature, flexible, and well supported standards-based mechanism for interacting with directory servers.
LDAP will allow you to login via Form and Basic Authentication
$action.getHelper().renderConfluenceMacro("$codeS$body$codeE")
Security Assertion Markup Language (SAML) is a login standard that helps users access applications based on sessions in another context. It’s a single sign-on (SSO) login method offering more secure authentication (with a better user experience) than usernames and passwords.
SAML will redirect you to the provider login page, so no login page is required.
Currently it is under development, but Microsoft SSO is supported
You need to add the callback url (e.g. http://localhost:8080)/saga/auth/callback) to your Authentication provider
$action.getHelper().renderConfluenceMacro("$codeS$body$codeE")
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:
curl --location --request GET 'http://localhost:8080/saga/api/client/process/units' \ --header 'Authorization: Basic <Base64(USERNAME:PASSWORD)>'
This method is recommended when having communication between services without user interaction.
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>
This API Keys, must be created in the Credentials section inside the Tools Menu. This keys can only be created by an authenticated user
curl --location --request GET 'http://localhost:8080/saga/api/client/process/units' \ --header 'Authorization: Saga <API_KEY>'