mirror of
https://github.com/kanidm/kanidm.git
synced 2025-02-23 20:47:01 +01:00
fix(docs): capitalization fixes (#2659)
This commit is contained in:
parent
ce526012da
commit
9c40a18b01
|
@ -35,9 +35,9 @@ Due to how web browsers and webauthn work, any matching domain name or subdomain
|
||||||
domain may have access to cookies within a browser session. An example is that `host.a.example.com`
|
domain may have access to cookies within a browser session. An example is that `host.a.example.com`
|
||||||
has access to cookies from `a.example.com` and `example.com`.
|
has access to cookies from `a.example.com` and `example.com`.
|
||||||
|
|
||||||
For this reason your kanidm host (or hosts) should be on a unique subdomain, with no other services
|
For this reason your Kanidm host (or hosts) should be on a unique subdomain, with no other services
|
||||||
registered under that subdomain. For example, consider `idm.example.com` as a subdomain for
|
registered under that subdomain. For example, consider `idm.example.com` as a subdomain for
|
||||||
exclusive use of kanidm. This is _inverse_ to Active Directory which often has it's domain name
|
exclusive use of Kanidm. This is _inverse_ to Active Directory which often has it's domain name
|
||||||
selected to be the parent (toplevel) domain (`example.com`).
|
selected to be the parent (toplevel) domain (`example.com`).
|
||||||
|
|
||||||
Failure to use a unique subdomain may allow cookies to leak to other entities within your domain,
|
Failure to use a unique subdomain may allow cookies to leak to other entities within your domain,
|
||||||
|
|
|
@ -4,7 +4,7 @@ This is a list of common questions that are generally raised by developers or te
|
||||||
|
|
||||||
## Why don't you use library/project X?
|
## Why don't you use library/project X?
|
||||||
|
|
||||||
A critical aspect of kanidm is the ability to test it. Generally requests to add libraries or
|
A critical aspect of Kanidm is the ability to test it. Generally requests to add libraries or
|
||||||
projects can come in different forms so I'll answer to a few of them:
|
projects can come in different forms so I'll answer to a few of them:
|
||||||
|
|
||||||
## Is the library in Rust?
|
## Is the library in Rust?
|
||||||
|
@ -25,7 +25,7 @@ parts. This creates production fragility and issues such as:
|
||||||
- Design choices of the project not being compatible with Kanidm's model
|
- Design choices of the project not being compatible with Kanidm's model
|
||||||
- Extra requirements for testing/production configuration
|
- Extra requirements for testing/production configuration
|
||||||
|
|
||||||
This last point is key. It is a critical part of kanidm that the following must work on all
|
This last point is key. It is a critical part of Kanidm that the following must work on all
|
||||||
machines, and run every single test in the suite.
|
machines, and run every single test in the suite.
|
||||||
|
|
||||||
```shell
|
```shell
|
||||||
|
|
Loading…
Reference in a new issue