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
| Field Name | Type | Mandatory | Description |
|---|---|---|---|
hashIterations | Number | Hashing Iteration value used by oAuth hasher to encrypt/compare passwords | |
seedLength | Number | Seed Length value used by oAuth hasher to encrypt/compare passwords |
3rd party login configuration
Location
In provision
OAuth allows third-party login via one of the below methods:
- 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.
- OpenAM login: SSO (Single Sign-On).
- LDAP (Lightweight Directory Access Protocol) login: Active directory login.
Configuration Sample
{
"oauth": {
"hashIterations": 1024, //used by hasher
"seedLength": 32, //used by hasher
}
}
Add Comment