Search Options

Display Count
Sort
Preferred Language
Advanced Search

Results 1 - 10 of 33 for challenges (0.06 seconds)

The search processing time has exceeded the limit. The displayed results may be partial.

  1. okhttp/src/jvmTest/kotlin/okhttp3/HeadersChallengesTest.kt

                "jdflkasdf\", qop=\"auth\", stale=\"FALSE\"",
            ).build()
        val challenges = headers.parseChallenges("WWW-Authenticate")
        assertThat(challenges.size).isEqualTo(1)
        assertThat(challenges[0].scheme).isEqualTo("Digest")
        assertThat(challenges[0].realm).isEqualTo("myrealm")
        val expectedAuthParams = mutableMapOf<String, String>()
        expectedAuthParams["realm"] = "myrealm"
    Created: Fri Apr 03 11:42:14 GMT 2026
    - Last Modified: Wed Mar 19 19:25:20 GMT 2025
    - 16.8K bytes
    - Click Count (0)
  2. okhttp/src/commonJvmAndroid/kotlin/okhttp3/Response.kt

      /**
       * Returns the RFC 7235 authorization challenges appropriate for this response's code. If the
       * response code is 401 unauthorized, this returns the "WWW-Authenticate" challenges. If the
       * response code is 407 proxy unauthorized, this returns the "Proxy-Authenticate" challenges.
       * Otherwise this returns an empty list of challenges.
       *
       * If a challenge uses the `token68` variant instead of auth params, there is exactly one
    Created: Fri Apr 03 11:42:14 GMT 2026
    - Last Modified: Mon Jul 28 14:39:28 GMT 2025
    - 18.1K bytes
    - Click Count (0)
  3. okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/http/RetryAndFollowUpInterceptor.kt

        if (header.matches("\\d+".toRegex())) {
          return Integer.valueOf(header)
        }
        return Integer.MAX_VALUE
      }
    
      companion object {
        /**
         * How many redirects and auth challenges should we attempt? Chrome follows 21 redirects; Firefox,
         * curl, and wget follow 20; Safari follows 16; and HTTP/1.0 recommends 5.
         */
        private const val MAX_FOLLOW_UPS = 20
      }
    Created: Fri Apr 03 11:42:14 GMT 2026
    - Last Modified: Tue Jan 27 09:00:39 GMT 2026
    - 12.5K bytes
    - Click Count (0)
  4. src/test/java/jcifs/http/NtlmServletTest.java

        }
    
        /**
         * Test the service method when no Authorization header is present and no session exists.
         * Expects a 401 Unauthorized response with NTLM and Basic authentication challenges.
         * @throws ServletException
         * @throws IOException
         */
        @Test
        void testService_NoAuthHeader_NoSession() throws ServletException, IOException {
            ntlmServlet.init(servletConfig);
    Created: Sun Apr 05 00:10:12 GMT 2026
    - Last Modified: Thu Aug 21 04:51:33 GMT 2025
    - 11.5K bytes
    - Click Count (0)
  5. src/test/java/jcifs/http/NtlmHttpFilterTest.java

            // Since we can't mock the internal transport operations easily without real network,
            // we'll test the simpler case where no NTLM negotiation is needed
            when(request.getHeader("Authorization")).thenReturn(null);
    
            filter.doFilter(request, response, filterChain);
    
            // Should challenge the client
    Created: Sun Apr 05 00:10:12 GMT 2026
    - Last Modified: Thu Aug 21 04:51:33 GMT 2025
    - 12.8K bytes
    - Click Count (0)
  6. okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/connection/ConnectPlan.kt

     *
     *  * [TCP handshake][connectSocket]
     *  * Optional [CONNECT tunnels][connectTunnel]. When using an HTTP proxy to reach an HTTPS server
     *    we must send a `CONNECT` request, and handle authorization challenges from the proxy.
     *  * Optional [TLS handshake][connectTls].
     *
     * Each step may fail. If a retry is possible, a new instance is created with the next plan, which
     * will be configured differently.
     */
    Created: Fri Apr 03 11:42:14 GMT 2026
    - Last Modified: Tue Jan 27 09:00:39 GMT 2026
    - 19.3K bytes
    - Click Count (2)
  7. src/main/java/jcifs/smb/NtlmUtil.java

         * @param password the password to hash
         * @param challenge the server challenge bytes
         * @return the calculated response
         * @throws GeneralSecurityException if a cryptographic error occurs
         */
        public static byte[] getNTLMResponse(final String password, final byte[] challenge) throws GeneralSecurityException {
            return getNTLMResponse(getNTHash(password), challenge);
        }
    
        /**
    Created: Sun Apr 05 00:10:12 GMT 2026
    - Last Modified: Sat Aug 30 05:58:03 GMT 2025
    - 15.1K bytes
    - Click Count (0)
  8. src/main/java/org/codelibs/fess/sso/spnego/SpnegoAuthenticator.java

         * extracts the user principal from successful authentication.
         *
         * @return The login credential containing the authenticated username,
         *         an ActionResponseCredential for authentication challenges,
         *         or null if no authentication information is available
         * @throws SsoLoginException if SPNEGO authentication fails
         */
        @Override
        public LoginCredential getLoginCredential() {
    Created: Tue Mar 31 13:07:34 GMT 2026
    - Last Modified: Sun Mar 15 08:18:23 GMT 2026
    - 18.2K bytes
    - Click Count (3)
  9. docs/sts/web-identity.md

    Provider they wish to use (the `MINIO_IDENTITY_OPENID_DISPLAY_NAME` value is shown here). The user is then redirected to the OpenID provider's login page and performs necessary login actions (e.g. entering credentials, responding to MFA authentication challenges, etc). After successful login, the user is redirected back to the MinIO console. This redirect URL is specified as a parameter by MinIO when the user is redirected to the OpenID Provider in the beginning. For some setups, extra configuration may...
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Tue Aug 12 18:20:36 GMT 2025
    - 18.9K bytes
    - Click Count (0)
  10. okhttp/src/commonJvmAndroid/kotlin/okhttp3/EventListener.kt

       *
       * The network response's status code is most influential when deciding how to follow up:
       *
       *  * For redirects (301: Moved Permanently, 302: Temporary Redirect, etc.)
       *  * For auth challenges (401: Unauthorized, 407: Proxy Authentication Required.)
       *  * For client timeouts (408: Request Time-Out.)
       *  * For server failures (503: Service Unavailable.)
       *
    Created: Fri Apr 03 11:42:14 GMT 2026
    - Last Modified: Tue Oct 07 21:03:04 GMT 2025
    - 24.9K bytes
    - Click Count (0)
Back to Top