minio/internal/config/identity/openid
Harshavardhana 9d07cde385
use crypto/sha256 only for FIPS 140-2 compliance (#14983)
It would seem like the PR #11623 had chewed more
than it wanted to, non-fips build shouldn't really
be forced to use slower crypto/sha256 even for
presumed "non-performance" codepaths. In MinIO
there are really no "non-performance" codepaths.
This assumption seems to have had an adverse
effect in certain areas of CPU usage.

This PR ensures that we stick to sha256-simd
on all non-FIPS builds, our most common build
to ensure we get the best out of the CPU at
any given point in time.
2022-05-27 06:00:19 -07:00
..
provider Add support for multiple OpenID providers with role policies (#14223) 2022-04-28 18:27:09 -07:00
ecdsa-sha3_contrib.go move to jwt-go v4 with correct releases (#13586) 2021-11-05 12:20:08 -07:00
help.go Add "enable" to config help (#14866) 2022-05-05 04:17:04 -07:00
jwks.go rename all remaining packages to internal/ (#12418) 2021-06-01 14:59:40 -07:00
jwks_test.go run gofumpt cleanup across code-base (#14015) 2022-01-02 09:15:06 -08:00
jwt.go Reorganize OpenID config (#14871) 2022-05-05 13:40:06 -07:00
jwt_test.go Add support for multiple OpenID providers with role policies (#14223) 2022-04-28 18:27:09 -07:00
openid.go use crypto/sha256 only for FIPS 140-2 compliance (#14983) 2022-05-27 06:00:19 -07:00
providercfg.go Reorganize OpenID config (#14871) 2022-05-05 13:40:06 -07:00
rsa-sha3_contrib.go move to jwt-go v4 with correct releases (#13586) 2021-11-05 12:20:08 -07:00