When running run-cluster from the Toolchain command, a bunch of test domains are set up in a local Kubernetes cluster.
You can use these domains to test and evaluate Uitsmijter.
This domain does not have an endpoint. This domain is used for tests and return a 404 page not found when called.
In cookbooks, a page served by a nginx container, you will find delicious recipes. Login is restricted via interceptor mode. Every user
that ends on @example.com (like me@example.com) with any password will be granted.
The Cookbook is managed by the cheese tenant. The login domain is: login.example.com
The goat page is an addition the cookbooks page, and it is also part of the cheese tenant. The information about goat cheese on an Uitsmijter is restricted via interceptor mode. Since cookbooks and goat shares the same interceptor cookie domain and the same login domain (login.example.com), you are already loged on goat if you are login on cookbooks.
Because the goat page is managed by the same tenant as the cookbooks, every user that ends on @example.com (like me@example.com) with
any password will be granted, too.
Another static page, managed by the cheese tenant and secured by interceptor mode.
Like goat and cookbooks, every user that ends on @example.com (like me@example.com) with
any password will be granted.
spa is the simplest form of a single page application login. It’s for testing purpose only.
id.example.com is the main domain for Uitsmijter for the cheese tenant.
If you are logged in to one oft the pages of the tenant ( cookbooks.example.com, goat.example.com, or toast.example.com ) You can see your payload when visiting https://id.example.com Similar to this output:
Payload: [profile: "[name: "Test User"]", tenant: "cheese/cheese", user: "me@example.com", responsibility: "dbf0dea75e338e296e034be7b3d69aab4407771f", exp: "1710602009.281026", sub: "me@example.com", role: "user"]
If you are logged out, a login mask is presented.
This domain is used as a proxy domain for the interceptor mode of the cheese tenant. The configuration of a proxy page is described on the interceptor mode documentation page.
When this page https://login.example.com is called up directly, an Uitsmijter error ERRORS.NO_TENANT is displayed,
because Uitsmijter does not know which page you are trying to login for. Proxy pages can only be accessed via a referrer registered in the tenant.
The missing-tenant domain is set as a secondary ingress to login.example.com, but not registered inside the tenant configuration.
Whenever you call this domain a ERRORS.NO_TENANT error should be presented.
So even if you pass a callee url to the missing-tenan domain, like https://missing-tenant.example.com/?for=https://goat.example.com/&mode=interceptor Uitsmijter have to deny the login!
On this page of the ham tenant you can read the story about Hank and Ellie. It is about an unexpected friendship. The page is served by a nginx contaienr and secured via interceptor mode.
Because the ham tenant turned the silen_login mode off, you are not logged in to page when you are logged in to shop.
Every user that ends on @example.com (like me@example.com) with any password will be granted.
Like page shop is also a static webpage served by nginx and secured via interceptor mode.
Because the ham tenant turned the silent_login mode off, you are not logged in to page when you are logged in to shop. You can not switch back and forth page and shop without login again, because the domain is bound to the token when silent_login is disabled.
Because this domain belongs to the same tenant as page.ham.test, the same login credentials (every user that ends
on @example.com, like me@example.com with any password) will be granted.
This domain is only used in tests as a redirect url.
This domain is only used in tests as a redirect url.
login.ham.test is the main domain for Uitsmijter for the ham tenant. This domain is possible not used any longer and will be removed!
id.ham.com is the interceptor proxy domain to log in via Uitsmijter. Proxy domains are necessary for interceptors and described on interceptor mode documentation page.
Ham does have customized templates, so the login page will look different from the default Uitsmijter login page of the chease tenant.
If you are logged in to one oft the pages of the tenant (page.ham.test or shop.ham.test)
Internal S3-Server to store customized templates
Credentials:
- access_key:
admin - secret_key:
adminSecretKey
This domain hosts the blog of the Bread And Butter Company. The blog is served by a nginx and secured
via interceptor mode.
Every user that ends on @example.com (like me@example.com) with any password will be granted.
Because the bnbc tenant turned the silen_login mode on, you are logged in to blog if you are logged in to shop.
Maya and Liam (The owners of the Bread And Butter Company) does have a shop, too. The shop is served by a nginx and secured via interceptor mode.
Because this domain belongs to the same tenant as blog.bnbc.example, the same login credentials (every user that ends
on @example.com, like me@example.com with any password) will be granted.
The bnbc tenant turned the silent_login mode on, so you are logged in to shop if you are already logged in to blog.
login.bnbc.example is the interceptor proxy domain to log in via Uitsmijter. Proxy domains are necessary for interceptors and described on interceptor mode documentation page.
You can see your payload when loged in via https://login.bnbc.example/?for=https://shop.bnbc.example/&mode=interceptor
This domain is only used in tests as a redirect url.
This domain is only used in tests as a redirect url.
This domain is the base domain of the Uitsmijter deployment. It handles this domains:
- test.localhost
- uitsmijter.localhost
All users are granted.