-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: changes for multitenancy dashboard #91
Conversation
api_spec.yaml
Outdated
|
||
- `null`: When set to `null`, the SDK will use firstFactors defined in the SDK | ||
- `[]` (empty array): No first factors would be enabled for the tenant | ||
- non-empty array: The first factors that are enabled for the tenant |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These three points are very unclear.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For example when you say "the SDK will use" - what SDK? This is just an API spec. Another example, is non-empty array: The first factors that are enabled for the tenant
-> when reading it, it makes no sense.
api_spec.yaml
Outdated
|
||
If first factors are not specified while creating a new connection uri domain, all the login methods will be enabled by default. | ||
|
||
`requiredSecondaryFactors` can be set to null to remove all entries in the core, or a non empty string array to be updated in the core. Setting of empty array is disallowed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
right. But what is the effect or removing it and setting it in the core? Please be clear. And make it a bullet point like you have done for firstFactors
api_spec.yaml
Outdated
|
||
- `null`: When set to `null`, the SDK will use firstFactors defined in the SDK | ||
- `[]` (empty array): No first factors would be enabled for the tenant | ||
- non-empty array: The first factors that are enabled for the tenant |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What are the values that it can accept if its non empty
@@ -5267,12 +5367,82 @@ paths: | |||
'500': | |||
$ref: '#/components/responses/500' | |||
|
|||
/recipe/multitenancy/connectionuridomain/list/v2: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
also mention the possible factors that can be in the firstFactors and requiredSecondaryFactors
No description provided.