...
hashIterations
...
Hashing Iteration value used by oAuth hasher to encrypt/compare passwords
...
seedLength
...
Seed Length value used by oAuth hasher to encrypt/compare passwords
...
Introduction
Provisioning is a configuration that all SOAJS micro-services can acquire once you turn on multi-tenant for them.
Once a service becomes multi-tenant, you can provide custom tenant configuration to it at run time.
If you have 2 tenants that can access the oAuth service, then the provisioned configuration for each tenant will be loaded once that tenant invokes an API in oAuth.
The below configuration is supported by the oAuth micro-service and can be configured & changed at the tenant level under the Manage Pillar.
Configuration Details
...
Like all SOAJS microservices, OAuth microservice has different layers of configuration. Local configuration, tenant-level configuration if the microservice is a multitenant one, and registry configuration. Moreover, OAuth can have a custom separate database for tokens and users.
Configuration Layers
1 - Tenant service configuration
This configuration is on the tenant level. OAuth configuration can be added from SOAJS Console and will exist under the tenant key configuration object.
Configuration Sample
| Code Block | |||
|---|---|---|---|
|
...
|
...
{
"oauth": {
"hashIterations": 1024, //used by hasher
"seedLength": 32, //used by hasher
}
}...
Steps to add tenant-level configuration
2 - Registry (Environment) configuration
This configuration is on the environment level. OAuth configuration can be added from SOAJS Console also.
3 - Separate Database for tokens and users
OAuth can have a separate database that can be added from Deploy tab in SOAJS Console → Databases
Third-Party configuration
| Info | ||
|---|---|---|
| ||
In provision |
...
- key configuration |
Passport Login: Define application keys for passport integration. Currently supporting Azure, Github, Twitter, Facebook, and Google.
...
Got to the link for more information and an example of the configuration.OAuth allows third-party login via one of the below methods:
OpenAM login: SSO (Single Sign-On).
LDAP (Lightweight Directory Access Protocol) login: Active directory login.