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

Removed old v3 and v4 docs #7402

Merged
merged 2 commits into from
Jun 18, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion website/docs/using-unleash/deploy/getting-started.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ Unleash started on http://localhost:4242

To run multiple replicas of Unleash simply point all instances to the same database.

**Unleash v4:** The first time Unleash starts it will create a default user which you can use to sign-in to you Unleash instance and add more users with:
The first time Unleash starts it will create a default user which you can use to sign-in to you Unleash instance and add more users with:

- username: `admin`
- password: `unleash4all`
Expand Down
2 changes: 0 additions & 2 deletions website/docs/using-unleash/deploy/google-auth-hook.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,8 +6,6 @@ title: Google Auth Hook

This part of the tutorial shows how to create a sign-in flow for users and integrate with Unleash server project. The implementation assumes that I am working in `localhost` with `4242` port.

**If you are still using Unleash v3 you need to follow the [google-auth-hook-v3](google-auth-v3)**

This is a simple `index.ts` server file.

```javascript
Expand Down
254 changes: 0 additions & 254 deletions website/docs/using-unleash/deploy/google-auth-v3.md

This file was deleted.

90 changes: 0 additions & 90 deletions website/docs/using-unleash/deploy/securing-unleash-v3.md

This file was deleted.

2 changes: 0 additions & 2 deletions website/docs/using-unleash/deploy/securing-unleash.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,8 +2,6 @@
title: Securing Unleash
---

**If you are still using Unleash v3 you need to follow the [securing-unleash-v3](./securing-unleash-v3)**

> This guide is only relevant if you are using Unleash Open-Source. The Enterprise edition does already ship with multiple SSO options, such as SAML 2.0, OpenID Connect.

Unleash Open-Source v4 comes with username/password authentication out of the box. In addition Unleash v4 also comes with API token support, to make it easy to handle access tokens for Client SDKs and programmatic access to the Unleash APIs.
Expand Down