v0.5.0 optional tls channel binding for scram
This commit is contained in:
1 parent
5cf0a93676
commit
b5524a3b9d
6 files changed
+139
-16
No files matched your search
@@ -7,8 +7,9 @@
|
||||
// before the application trusts the authentication result.
|
||||
//
|
||||
// The SCRAM exchange uses a package-specific Argon2id/JSON protocol; it is not
|
||||
// interoperable with the standard SASL SCRAM-SHA-256 mechanism. Applications must
|
||||
// supply authenticated TLS, request limits, rate limits, and authorization.
|
||||
// interoperable with the standard SASL SCRAM-SHA-256 mechanism. WithChannelBinding
|
||||
// commits a proof to the TLS channel. Applications must supply authenticated TLS,
|
||||
// request limits, rate limits, and authorization.
|
||||
//
|
||||
// NewJWT and NewJWTRSA create reusable, concurrent token managers. Configure an
|
||||
// issuer and audience for each service. ValidateToken requires expiration and a
|
||||
|
||||
Reference in new issue
Block a user