generated from nginx/template-repository
-
Notifications
You must be signed in to change notification settings - Fork 120
fix: clarify what users should do if they don't have a TENANT_NAME #997
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
Merged
Merged
Changes from 3 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
31b91b6
fix: clarify what users should do if they don't have a TENANT_NAME
mjang 5114456
Update secure your fleet with include
mjang 16229d6
Update content/includes/nginx-one/cloud-access.md
mjang b70726e
Apply suggestions from code review
mjang 5a997e2
Merge branch 'main' into fix-add-tenant-name
mjang 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 hidden or 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 |
---|---|---|
|
@@ -4,15 +4,22 @@ files: | |
- content/nginx-one/getting-started.md | ||
--- | ||
|
||
Confirm that an F5 Distributed Cloud tenant has been provisioned for you. | ||
Confirm that an F5 Distributed Cloud tenant has been provisioned for you. To do so: | ||
|
||
1. Log in to [MyF5](https://my.f5.com/manage/s/) and review your subscriptions. | ||
2. Look for **Distributed Cloud** in one of your subscriptions. This could appear under an NGINX subscription or a Distributed Cloud subscription. | ||
|
||
If you don’t see **Distributed Cloud** in any subscription, contact your F5 account team or Customer Success Manager. | ||
|
||
When your tenant is created, you or someone in your organization should receive an email from **[email protected]** asking you to set your password. The account name in bold in the email is your tenant name. | ||
When you have a subscription, you or someone in your organization should have an email from [email protected] asking you to update your password. | ||
|
||
Go to `https://<TENANT_NAME>.console.ves.volterra.io/` to access F5 Distributed Cloud. | ||
If you have never signed in, select **Forgot Password?** on the sign-in page. | ||
Alternatively, ask someone in your organization with access to add you as a user in your tenant with a role that includes permissions for NGINX One Console. | ||
That email includes an account name, which is the TENANT_NAME. | ||
|
||
To access F5 Distributed Cloud, navigate to https://INSERT_YOUR_TENANT_NAME.console.ves.volterra.io/. If you have never logged in, select the **Forgot Password?** option in the log in screen. Alternatively, if someone within your organization has access, ask them to add you as a user within your tenant with access to NGINX One Console. | ||
mjang marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
||
If you do not know your TENANT_NAME, you can: | ||
|
||
- Email [email protected] to get your username and TENANT_NAME. | ||
- If you have a dedicated F5 tenant administrator, ask them to: | ||
- Provide a username for your tenant | ||
- Ask them to reset your password |
This file contains hidden or 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 |
---|---|---|
|
@@ -27,11 +27,7 @@ If you already have accessed F5 Distributed Cloud and have NGINX instances avail | |
|
||
### Confirm access to the F5 Distributed Cloud | ||
|
||
Confirm an F5 Distributed Cloud tenant has been provisioned for you. Log in to the [MyF5](https://my.f5.com) customer portal and review your subscriptions. You should see within one of your subscriptions "Distributed Cloud". This could be in either an NGINX subscription or a Distributed Cloud. If the above does not appear in any of your subscriptions, reach out to either your F5 Account Team or Customer Success Manager. | ||
|
||
With access, you or someone in your organization should have an email from [email protected] asking you to update your password when the tenant was created. The account name referenced in the email in bold is the tenant name. | ||
|
||
Go to https://INSERT_YOUR_TENANT_NAME.console.ves.volterra.io/ to access F5 Distributed Cloud. If you have never logged in, select the **Forgot Password?** option in the log in screen. Alternatively, if someone within your organization has access, ask them to add you as a user within your tenant with a role providing permissions for NGINX One. | ||
{{< include "/nginx-one/cloud-access.md" >}} | ||
|
||
### Confirm access to NGINX One Console in the F5 Distributed Cloud | ||
|
||
|
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.
Uh oh!
There was an error while loading. Please reload this page.