chore: rename configuration to settings (#11568)

# Which Problems Are Solved

naming inconsistencies: Configuration <-> Settings

# How the Problems Are Solved


# Additional Changes


# Additional Context

- Closes #11282
This commit is contained in:
Wim Van Laer
2026-02-18 14:25:42 +01:00
committed by GitHub
parent 64065bbe3c
commit 699ed17918
129 changed files with 359 additions and 359 deletions
+3 -3
View File
@@ -27,7 +27,7 @@ then open [http://localhost:3000](http://localhost:3000) with your browser to se
## Setup Application and Get Keys
Before we can start building our application, we have to do a few configuration steps in ZITADEL Console.
Before we can start building our application, we have to do a few setup steps in ZITADEL Console.
You will need to provide some information about your app.
Navigate to your Project, then add a new application at the top of the page.
@@ -54,10 +54,10 @@ After successful app creation, a pop-up will appear, showing the app's client ID
Now that you have your web application configured on the ZITADEL side, you can go ahead and integrate your NextJS app.
### Configuration
### Setup
NextAuth.js exposes a REST API which is used by your application.
To setup your configuration, create a file called `src/lib/auth.ts`.
To setup your auth, create a file called `src/lib/auth.ts`.
You can directly import the ZITADEL provider from [next-auth](https://next-auth.js.org/providers/zitadel).
```ts reference