minio/Chart.yaml apiVersion: v1 appVersion: RELEASE.2021-08-25T00-41-18Z description: Multi-Cloud Object Storage home: https://min.io icon: https://min.io/resources/img/logo/MINIO_wordmark.png keywords: - storage - object-storage - S3 maintainers: - email: ******@****.*** name: MinIO, Inc name: minio sources: - https://github.com/minio/minio version: 1.0.5 minio/values.yaml ## Provide a name in place of minio for `app:` labels ## nameOverride: "" ## Provide a name to substitute for the full names of resources...

minio/Chart.yaml apiVersion: v1 appVersion: RELEASE.2021-08-25T00-41-18Z description: Multi-Cloud Object Storage home: https://min.io icon: https://min.io/resources/img/logo/MINIO_wordmark.png keywords: - storage - object-storage - S3 maintainers: - email: ******@****.*** name: MinIO, Inc name: minio sources: - https://github.com/minio/minio version: 2.0.0 minio/values.yaml ## Provide a name in place of minio for `app:` labels ## nameOverride: "" ## Provide a name to substitute for the full names of resources...

  
  When configuring a JWT authenticator:
  
  If username.expression uses 'claims.email', then 'claims.email_verified' must be used in
  username.expression or extra[*].valueExpression or claimValidationRules[*].expression.
  An example claim validation rule expression that matches the validation automatically
  applied when username.claim is set to 'email' is 'claims.?email_verified.orValue(true) == true'. 

[@caesarxuchao](https://github.com/caesarxuchao))

* Using kubectl gcp auth plugin with a Google Service Account to authenticate to a cluster now additionally requests a token with the  "userinfo.email" scope. This way, users can write ClusterRoleBindings/RoleBindings with the email address of the service account directly. (This is a breaking change if the numeric uniqueIDs of the Google service accounts were being used in RBAC role bindings. The behavior can be overridden by explicitly...

* OIDC authentication now allows tokens without an "email_verified" claim when using the "email" claim. If an "email_verified" claim is present when using the "email" claim, it must be `true`. ([#61508](https://github.com/kubernetes/kubernetes/pull/61508), [@rithujohn191](https://github.com/rithujohn191))

- When configuring a JWT authenticator:
  
  If `username.expression` used 'claims.email', then 'claims.email_verified' must have been used in `username.expression` or `extra[*].valueExpression` or `claimValidationRules[*].expression`. An example claim validation rule expression that matches the validation automatically applied when `username.claim` is set to 'email' is 'claims.?email_verified.orValue(true) == true'.

  <mime-type type="application/vnd.oma.poc.optimized-progress-report+xml"/>
  <mime-type type="application/vnd.oma.xcap-directory+xml"/>
  <mime-type type="application/vnd.omads-email+xml"/>
  <mime-type type="application/vnd.omads-file+xml"/>
  <mime-type type="application/vnd.omads-folder+xml"/>
  <mime-type type="application/vnd.omaloc-supl-init"/>

Lóránt Pintér <******@****.***>
Lóránt Pintér <******@****.***> <lorant.pinter@gmail.com>
Lóránt Pintér <******@****.***> <******@****.***>
Marcin Erdmann <******@****.***> <erdi84@gmail.com>
Marco Vermeulen <******@****.***> <vermeulen.mp@gmail.com>
Mark Vieira <******@****.***> <portugee@gmail.com>
Michael Barnathan <******@****.***> <******@****.***>

        }
    }

    // Test with different hostnames
    public void test_differentHostnames() {
        String[] hostnames = { "smtp.gmail.com", "mail.example.com", "localhost", "192.168.1.1" };

        for (String hostname : hostnames) {
            ComponentUtil.setFessConfig(new FessConfig.SimpleImpl() {

* **When using OIDC authentication and specifying --oidc-username-claim=email, an `"email_verified":true` claim must be returned from the identity provider. ([#36087](https://github.com/kubernetes/kubernetes/pull/36087), [@ericchiang](https://github.com/ericchiang))**