Skip to content

Conversation

@HannesSandberg
Copy link
Contributor

The next part of ABAC documentation, based on top of #2728

This PR contains the documentation for the SHOW AUTH RULES command.

@HannesSandberg HannesSandberg added the team-cypher-operations Cypher operations should review this label Jan 27, 2026
@Hunterness Hunterness self-assigned this Jan 27, 2026
Copy link
Contributor

@phil198 phil198 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks nice. A couple of minor things

| Type

| name
| The name of auth rule as defined in the `CREATE` or `RENAME AUTH RULE` command.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| The name of auth rule as defined in the `CREATE` or `RENAME AUTH RULE` command.
| The name of the auth rule as defined in the `CREATE` or `RENAME AUTH RULE` command.

| STRING

| enabled
| Whether the auth rule is enabled or not. This column will have the value true when the auth rule is enabled, and false when it is not.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| Whether the auth rule is enabled or not. This column will have the value true when the auth rule is enabled, and false when it is not.
| Whether the auth rule is enabled or not. This column will have the value `true` when the auth rule is enabled, and `false` when it is not.

Do we normally do this for booleans?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, might be nice to add something like
When an auth rule is disabled it will not be evaluated and so users cannot receive its roles
even though this is somewhat stating the obvious.

| BOOLEAN

| roles
| The roles which have been granted to the auth rule via one or more `GRANT ROLE … TO AUTH RULE …` commands. This column will return null if the executing user is missing or denied the `SHOW ROLES` privilege.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| The roles which have been granted to the auth rule via one or more `GRANT ROLE … TO AUTH RULE …` commands. This column will return null if the executing user is missing or denied the `SHOW ROLES` privilege.
| The roles which have been granted to the auth rule via one or more `GRANT ROLE … TO AUTH RULE …` commands. This column will return `null` if the executing user is missing or denied the `SHOW ROLES` privilege.

Copy link
Contributor

@Hunterness Hunterness left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comments 💬

== Listing auth rules

You can list all auth rules using the Cypher command `SHOW AUTH RULES`.
It produces a table containing a single row per auth rule with the following columns:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

might be nice to explicitly state that all columns are returned by default?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure, to me it feels odd to explicitly state it, when we say it produces a table with the following columns.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we point it out in general, or have labels in the table for which are default when it's a mix

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

though looking at show users we don't seem to do it there 🤷

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I looked at the users and the roles pages and could not find that we state it there.

The functions, `date`, `datetime`, `localdatetime`, `localtime` and `time` are only supported when an input argument is used.
====

== Listing auth rules
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we want a introduced in version label for this?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think soo, since none of it is released yet (they are hiding behind a feature flag).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so the whole page should then get the label for when it's released, makes sense

Co-authored-by: Therese Magnusson <scout.therese@gmail.com>
@neo4j-docops-agent
Copy link
Collaborator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

team-cypher-operations Cypher operations should review this

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants