Skip to content
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

User1 status check #23

Open
roberttruscott opened this issue Nov 18, 2019 · 2 comments
Open

User1 status check #23

roberttruscott opened this issue Nov 18, 2019 · 2 comments

Comments

@roberttruscott
Copy link

content/Policy/drupal-7/user1.policy.yml defaults to 1 for account status. This is active, as noted in the file. However, when the check fails (i.e. account status is inactive), it reports as: "User #1 is not secure. Status is not set correctly. Should be inactive."

If User 1 is set the active, the check clears and reports: "User #1 is locked down. ... Status is set to 1"

@fiasco
Copy link
Contributor

fiasco commented Nov 24, 2019

Thanks for the feedback @roberttruscott - do you have a view on what you think it should say?

@roberttruscott
Copy link
Author

Josh,

If the check is intended to report on status of user 1 and the desired outcome is to verify status is locked/inactive:

This bit -
status:
default: 1
type: boolean
description: |
Ensures the uid:1 user status reflects the same as this argument. Defaults
to active (1).

Should probably change to -
status:
default: 0
type: boolean
description: |
Ensures the uid:1 user status reflects the same as this argument. Defaults
to inactive (0).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants