Search Options

Results per page
Sort
Preferred Languages
Advance

Results 511 - 520 of 613 for description_ (2.42 sec)

  1. cmd/sts-handlers.go

    	// Validate the authentication result here so that failures will be audit-logged.
    	if apiErrCode != ErrNone {
    		stsErr := apiToSTSError(apiErrCode)
    		// Borrow the description error from the API error code
    		writeSTSErrorResponse(ctx, w, stsErr, errors.New(errorCodes[apiErrCode].Description))
    		return
    	}
    
    	if err := claims.populateSessionPolicy(r.Form); err != nil {
    		writeSTSErrorResponse(ctx, w, ErrSTSInvalidParameterValue, err)
    		return
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Fri Aug 29 02:39:48 UTC 2025
    - 36.6K bytes
    - Viewed (0)
  2. CREDITS

    the terms of this License to the maximum extent possible; and (b)
    describe the limitations and the code they affect. Such description must
    be placed in a text file included with all distributions of the Covered
    Software under this License. Except to the extent prohibited by statute
    or regulation, such description must be sufficiently detailed for a
    recipient of ordinary skill to be able to understand it.
    
    5. Termination
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Thu Mar 13 05:29:51 UTC 2025
    - 1.8M bytes
    - Viewed (0)
  3. cmd/site-replication.go

    			accessKey:     change.Create.AccessKey,
    			secretKey:     change.Create.SecretKey,
    			sessionPolicy: sp,
    			claims:        change.Create.Claims,
    			name:          change.Create.Name,
    			description:   change.Create.Description,
    			expiration:    change.Create.Expiration,
    		}
    		_, _, err = globalIAMSys.NewServiceAccount(ctx, change.Create.Parent, change.Create.Groups, opts)
    		if err != nil {
    			return wrapSRErr(err)
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Fri Aug 29 02:39:48 UTC 2025
    - 184.7K bytes
    - Viewed (0)
  4. LICENSE

          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    
       Copyright {yyyy} {name of copyright owner}
    
    Registered: Thu Sep 04 15:34:10 UTC 2025
    - Last Modified: Thu Jun 14 07:45:22 UTC 2018
    - 11.1K bytes
    - Viewed (0)
  5. LICENSE

          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    
       Copyright [yyyy] [name of copyright owner]
    
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Tue Nov 22 19:44:46 UTC 2016
    - 11.1K bytes
    - Viewed (0)
  6. LICENSES/LICENSE

          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    
       Copyright [yyyy] [name of copyright owner]
    
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Fri May 08 04:49:00 UTC 2020
    - 11.3K bytes
    - Viewed (0)
  7. LICENSES/vendor/github.com/NYTimes/gziphandler/LICENSE

          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    
       Copyright 2016-2017 The New York Times Company
    
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Wed Feb 03 21:57:36 UTC 2021
    - 11.2K bytes
    - Viewed (0)
  8. LICENSES/vendor/github.com/container-storage-interface/spec/LICENSE

          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    
       Copyright {yyyy} {name of copyright owner}
    
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Fri May 08 04:49:00 UTC 2020
    - 11.3K bytes
    - Viewed (0)
  9. LICENSES/vendor/github.com/coreos/go-semver/LICENSE

          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    
       Copyright [yyyy] [name of copyright owner]
    
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Fri May 08 04:49:00 UTC 2020
    - 11.2K bytes
    - Viewed (0)
  10. LICENSES/vendor/github.com/google/btree/LICENSE

          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    
       Copyright [yyyy] [name of copyright owner]
    
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Fri May 08 04:49:00 UTC 2020
    - 11.2K bytes
    - Viewed (0)
Back to top