Replace keypair by key pair
Replace adress by address
This commit is contained in:
parent
442c839595
commit
1464c1bbfa
2 changed files with 2 additions and 2 deletions
|
@ -2,7 +2,7 @@
|
|||
=== Realm Key Pairs
|
||||
|
||||
The authentication protocols that are used by {{book.project.name}} require cryptographic signatures and sometimes even
|
||||
encryption. {{book.project.name}} uses a asymetric keypair, a private and public key to accomplish this. When a realm
|
||||
encryption. {{book.project.name}} uses a asymmetric key pair, a private and public key to accomplish this. When a realm
|
||||
is created a key pair is automatically generated. It is recommended that you cycle this key pair occasionally. How often
|
||||
you do this is dependent on your organizational needs and security requirements as you have to make sure every application
|
||||
that needs the public or certificate of your realm get this updated. This can be a lot of work!
|
||||
|
|
|
@ -18,7 +18,7 @@ The `Require SSL` option allows you to pick the SSL Mode you want. Here is an e
|
|||
|
||||
external requests::
|
||||
Users can interact with {{book.project.name}} so long as they stick to private IP addresses like `localhost`, `127.0.0.1`, `10.0.x.x`, `192.168.x.x`, and `172..16.x.x`.
|
||||
If you try to access {{book.project.name}} from a non-private IP adress you will get an error.
|
||||
If you try to access {{book.project.name}} from a non-private IP address you will get an error.
|
||||
|
||||
none::
|
||||
{{book.project.name}} does not require SSL. This should really only be used in development when you are playing around with things and don't want to bother
|
||||
|
|
Loading…
Reference in a new issue