1 # Which URL are we accessible at? This is used to determine the redirect URL
2 # and some user-accessible URLs.
5 # Should we serve /static ourself? This should usually be handled by the
6 # upstream Web server such as nginx(8) or OpenBSD httpd(8). However, this might
7 # be useful during development or when running behind relayd(8).
11 # Which protocol are we listening for? This may be set to "http" for
12 # plain HTTP, or "fcgi" for FastCGI. FastCGI is recommended for most
13 # purposes, and both nginx(8) and OpenBSD httpd(8) may easily be
14 # configured to serve FastCGI. However, if for any reason we need to
15 # run behind relayd(8) or another reverse proxy, http is available.
18 # Which network backend should we use? This is usually set to "tcp"
19 # for plain TCP, and "unix" for UNIX domain sockets.
22 # What is the address we should listen at? This is usually set to
23 # something like ":5555" for TCP, and a file path for UNIX domain
29 # What type of database should we use? Currently, only "sqlite" is
33 # What is the connection string to database? For SQLite, this is
34 # simply a path to the database file.
39 # What is our OAUTH2 client ID?
40 client 6d3106e1-a859-4e68-8115-8df599333fc6
42 # What is the OpenID Connect endpoint? The OpenID configuration is
43 # taken from this/.well-known/openid-configuration.
44 endpoint https://login.microsoftonline.com/ddd3d26c-b197-4d00-a32d-1ffd84c0c295
46 # [optional] This option may be used to override the OpenID authorize
47 # endpoint. This is generally necessary when using Microsoft's OpenID
48 # because their openid-configuration gives us the OAUTH 1.0 endpoint,
49 # while we need the OAUTH 2.0 endpoint.
50 authorize https://login.microsoftonline.com/ddd3d26c-b197-4d00-a32d-1ffd84c0c295/oauth2/v2.0/authorize