-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy path.env.example
More file actions
54 lines (46 loc) · 2.59 KB
/
.env.example
File metadata and controls
54 lines (46 loc) · 2.59 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
# -----------------------------------------------------------------------------
# App Configuration
# -----------------------------------------------------------------------------
# The network port on which the Spring Boot server will listen for incoming
# connections. Change this if port 3000 is already in use on your system.
PORT=3000
# -----------------------------------------------------------------------------
# Session Configuration
# -----------------------------------------------------------------------------
# A long, random, and secret string used to sign the session and cookies.
# This prevents the session from being tampered with. It must be kept private.
# Generate a secure key using:
# openssl rand -hex 32
SESSION_SECRET="your-very-secret-and-strong-session-key"
# The total duration of the session in seconds. After this period of
# inactivity, the user will be effectively logged out.
# Default is 3600, which is 1 hour (60 * 60).
SESSION_DURATION=3600
# -----------------------------------------------------------------------------
# ZITADEL OpenID Connect (OIDC) Configuration
# -----------------------------------------------------------------------------
# The full domain URL of your ZITADEL instance. You can find this in your
# ZITADEL organization's settings.
# Example: https://my-org-a1b2c3.zitadel.cloud
ZITADEL_DOMAIN="https://your-zitadel-domain"
# The unique Client ID for your application, obtained from the ZITADEL Console.
# This identifier tells ZITADEL which application is making the request.
ZITADEL_CLIENT_ID="your-zitadel-application-client-id"
# While the Authorization Code Flow with PKCE for public clients does not
# strictly require a client secret for OIDC specification compliance, Spring
# Security will still require a value for its internal configuration.
# Generate a secure key using:
# openssl rand -hex 32
ZITADEL_CLIENT_SECRET="your-randomly-generated-client-secret"
# The full URL where ZITADEL redirects the user after they have authenticated.
# This MUST exactly match one of the "Redirect URIs" you have configured in
# your ZITADEL application settings.
ZITADEL_CALLBACK_URL="http://localhost:3000/auth/callback"
# The internal URL within your application where users are sent after a
# successful login is processed at the callback URL.
# Defaults to "/profile" if not specified.
ZITADEL_POST_LOGIN_URL="/profile"
# The full URL where ZITADEL redirects the user after they have logged out.
# This MUST exactly match one of the "Post Logout Redirect URIs" configured
# in your ZITADEL application settings.
ZITADEL_POST_LOGOUT_URL="http://localhost:3000/auth/logout/callback"