-
Notifications
You must be signed in to change notification settings - Fork 26
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
Add notifications for linked users #142
Merged
renetapopova
merged 1 commit into
neo4j:dev
from
Hunterness:dev-linked-users-notifications
Sep 17, 2024
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2726,6 +2726,107 @@ Use `DATABASE *` without the parameter to revoke the privilege on all databases. | |
====== | ||
===== | ||
|
||
[#_neo_clientnotification_security_authprovidernotdefined] | ||
=== AuthProviderNotDefined | ||
|
||
.Notification details | ||
[cols="<1s,<4"] | ||
|=== | ||
|Code | ||
m|Neo.ClientNotification.Security.AuthProviderNotDefined | ||
|Title | ||
a|The auth provider is not defined. | ||
|Description | ||
a|The auth provider `<provider>` is not defined in the configuration. | ||
Verify that the spelling is correct or define `<provider>` in the configuration. | ||
|Severity | ||
m|INFORMATION | ||
|Category | ||
m|SECURITY | ||
|=== | ||
|
||
.Create a user with an auth provider that is not defined in the configuration | ||
==== | ||
Command:: | ||
+ | ||
[source, cypher] | ||
---- | ||
CREATE USER foo SET AUTH 'unknownProvider' { SET ID 'idString' } | ||
---- | ||
|
||
Description of the returned code:: | ||
The auth provider `unknownProvider` is not defined in the configuration. | ||
Verify that the spelling is correct or define `unknownProvider` in the configuration. | ||
|
||
Suggestions for improvement:: | ||
Make sure that the given provider is correct, or replace it if not. | ||
If it is correct, make sure to add it as a known auth provider in one or both of `dbms.security.authentication_providers` and `dbms.security.authorization_providers`. | ||
==== | ||
|
||
.Alter a user to add an auth provider that is not defined in the configuration | ||
==== | ||
Command:: | ||
+ | ||
[source, cypher] | ||
---- | ||
ALTER USER foo SET AUTH 'unknownProvider' { SET ID 'idString' } | ||
---- | ||
|
||
Description of the returned code:: | ||
The auth provider `unknownProvider` is not defined in the configuration. | ||
Verify that the spelling is correct or define `unknownProvider` in the configuration. | ||
|
||
Suggestions for improvement:: | ||
Make sure that the given provider is correct, or replace it if not. | ||
If it is correct, make sure to add it as a known auth provider in one or both of `dbms.security.authentication_providers` and `dbms.security.authorization_providers`. | ||
==== | ||
|
||
[#_neo_clientnotification_security_externalauthnotenabled] | ||
=== ExternalAuthNotEnabled | ||
|
||
.Notification details | ||
[cols="<1s,<4"] | ||
|=== | ||
|Code | ||
m|Neo.ClientNotification.Security.ExternalAuthNotEnabled | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This notification was an error in CIP-145 but was decided to be just a warning during implementation (to not lock out current external only users from being able to switch by first adding the new external only users to system before disabling their ways to log in) |
||
|Title | ||
a|External auth for user is not enabled. | ||
|Description | ||
a|Use setting `dbms.security.require_local_user` to enable external auth. | ||
Hunterness marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|Severity | ||
m|WARNING | ||
|Category | ||
m|SECURITY | ||
|=== | ||
|
||
.Create a user with an external auth provider when linked users are not enabled | ||
==== | ||
Command:: | ||
+ | ||
[source, cypher] | ||
---- | ||
CREATE USER foo SET AUTH 'exampleProvider' { SET ID 'idString' } | ||
---- | ||
|
||
Suggestions for improvement:: | ||
Enable linked users through the `dbms.security.require_local_user` setting. | ||
Until enabled, the new external auth will be ignored, and current external auth behaviors will continue to apply. | ||
==== | ||
|
||
.Alter a user to add an external auth provider when linked users are not enabled | ||
==== | ||
Command:: | ||
+ | ||
[source, cypher] | ||
---- | ||
ALTER USER foo SET AUTH 'exampleProvider' { SET ID 'idString' } | ||
---- | ||
|
||
Suggestions for improvement:: | ||
Enable linked users through the `dbms.security.require_local_user` setting. | ||
Until enabled, the new external auth will be ignored, and current external auth behaviors will continue to apply. | ||
==== | ||
|
||
[#_topology_notifications] | ||
== `TOPOLOGY` category | ||
|
||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
This notification was covered by CIP-145.