Skip to content

DOC-663 | Add missing info on autologin feature and private endpoints in AG #472

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Feb 20, 2024
Merged

DOC-663 | Add missing info on autologin feature and private endpoints in AG #472

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions site/content/3.10/arangograph/deployments/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -205,6 +205,12 @@ that it may take a few minutes to get activated.
Once enabled, you no longer have to fill in the `root` user and password of
your ArangoDB deployment.

{{< info >}}
If you use the auto login feature with AWS
[private endpoints](../deployments/private-endpoints.md), it is recommended
to switch off the `custom DNS` setting.
{{< /info >}}

This feature can be disabled at any time. You may wish to consider explicitly
disabling this feature in the following situations:
- Your workflow requires you to access the database UI using different accounts
Expand All @@ -214,6 +220,12 @@ disabling this feature in the following situations:
any access to ArangoGraph. Note, however, that it's possible to only give an
ArangoGraph user database UI access, without other ArangoGraph permissions.

{{< warning >}}
When the auto login feature is enabled, users cannot edit their permissions on
the ArangoDB database web interface as all permissions are managed by the
ArangoGraph platform.
{{< /warning >}}

Before getting started, make sure you are signed into ArangoGraph as a user
with one of the following permissions in your project:
- `data.deployment.full-access`
Expand Down
12 changes: 12 additions & 0 deletions site/content/3.11/arangograph/deployments/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -205,6 +205,12 @@ that it may take a few minutes to get activated.
Once enabled, you no longer have to fill in the `root` user and password of
your ArangoDB deployment.

{{< info >}}
If you use the auto login feature with AWS
[private endpoints](../deployments/private-endpoints.md), it is recommended
to switch off the `custom DNS` setting.
{{< /info >}}

This feature can be disabled at any time. You may wish to consider explicitly
disabling this feature in the following situations:
- Your workflow requires you to access the database UI using different accounts
Expand All @@ -214,6 +220,12 @@ disabling this feature in the following situations:
any access to ArangoGraph. Note, however, that it's possible to only give an
ArangoGraph user database UI access, without other ArangoGraph permissions.

{{< warning >}}
When the auto login feature is enabled, users cannot edit their permissions on
the ArangoDB database web interface as all permissions are managed by the
ArangoGraph platform.
{{< /warning >}}

Before getting started, make sure you are signed into ArangoGraph as a user
with one of the following permissions in your project:
- `data.deployment.full-access`
Expand Down
12 changes: 12 additions & 0 deletions site/content/3.12/arangograph/deployments/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -205,6 +205,12 @@ that it may take a few minutes to get activated.
Once enabled, you no longer have to fill in the `root` user and password of
your ArangoDB deployment.

{{< info >}}
If you use the auto login feature with AWS
[private endpoints](../deployments/private-endpoints.md), it is recommended
to switch off the `custom DNS` setting.
{{< /info >}}

This feature can be disabled at any time. You may wish to consider explicitly
disabling this feature in the following situations:
- Your workflow requires you to access the database UI using different accounts
Expand All @@ -214,6 +220,12 @@ disabling this feature in the following situations:
any access to ArangoGraph. Note, however, that it's possible to only give an
ArangoGraph user database UI access, without other ArangoGraph permissions.

{{< warning >}}
When the auto login feature is enabled, users cannot edit their permissions on
the ArangoDB database web interface as all permissions are managed by the
ArangoGraph platform.
{{< /warning >}}

Before getting started, make sure you are signed into ArangoGraph as a user
with one of the following permissions in your project:
- `data.deployment.full-access`
Expand Down