Skip to content
This repository has been archived by the owner on Jun 28, 2023. It is now read-only.

Statuses in The Readme #6

Closed
DamirSvrtan opened this issue Dec 18, 2013 · 1 comment
Closed

Statuses in The Readme #6

DamirSvrtan opened this issue Dec 18, 2013 · 1 comment

Comments

@DamirSvrtan
Copy link
Contributor

So the resources that have the status property are:

Application
Directory
Group
Account

Application, Directory and Group status values can be:

ENABLED and DISABLED

and Account has the two mentioned plus:

UNVERIFIED and LOCKED.

The LOCKED status isn't documented in the REST API docs. What is the difference between LOCKED and DISABLED?

Also, for the Application resource, it's clearly stated in the docs that ENABLED is the default status. It's clear for me that this is the same behavior for all 4 resources, but it should also be stated in the docs.

@lhazlewood
Copy link
Member

LOCKED was introduced to help support an upcoming feature. I can/should be removed entirely until we need it.

Accounts are ENABLED by default unless the Directory requires email verification for new accounts added to it. In this case, accounts in that Directory are UNVERIFIED (a sub-state of DISABLED) by default.

Once an UNVERIFIED account's email is verified, the account's status is automatically changed from UNVERIFIED to ENABLED.

@rdegges rdegges closed this as completed Sep 29, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants