- Sort Score
- Num 10 results
- Language All
Results 191 - 200 of 288 for oauth2 (0.05 seconds)
-
samples/slack/src/main/java/okhttp3/slack/SlackClient.java
}); System.out.printf("open this URL in a browser: %s\n", authorizeUrl); } /** Set the OAuth session for this client. */ public synchronized void initOauthSession(OAuthSession session) { this.session = session; this.notifyAll(); } /** Waits for an OAuth session for this client to be set. */ public synchronized void awaitAccessToken(Timeout timeout) throws InterruptedIOException {Created: Fri Dec 26 11:42:13 GMT 2025 - Last Modified: Sat Jan 12 03:31:36 GMT 2019 - 3.4K bytes - Click Count (0) -
samples/slack/src/main/java/okhttp3/slack/OAuthSessionFactory.java
import okhttp3.mockwebserver.MockWebServer; import okhttp3.mockwebserver.RecordedRequest; import okio.ByteString; /** * Runs a MockWebServer on localhost and uses it as the backend to receive an OAuth session. * * <p>Clients should call {@link #start}, {@link #newAuthorizeUrl} and {@link #close} in that order. * Clients may request multiple sessions. */Created: Fri Dec 26 11:42:13 GMT 2025 - Last Modified: Thu Aug 12 07:26:27 GMT 2021 - 3.8K bytes - Click Count (1) -
src/main/java/org/codelibs/fess/sso/SsoAuthenticator.java
* * This interface defines the contract for SSO authentication providers that can be * integrated with Fess. Implementations handle specific SSO protocols like SAML, * OAuth, SPNEGO, or other authentication mechanisms. Each authenticator is responsible * for obtaining login credentials, resolving user information, and managing SSO * lifecycle operations like logout and metadata exchange. */
Created: Sat Dec 20 09:19:18 GMT 2025 - Last Modified: Thu Jul 17 08:28:31 GMT 2025 - 2.2K bytes - Click Count (1) -
internal/config/identity/openid/jwt.go
return err } // Validate that matching clientID appears in the aud or azp claims. // REQUIRED. Audience(s) that this ID Token is intended for. // It MUST contain the OAuth 2.0 client_id of the Relying Party // as an audience value. It MAY also contain identifiers for // other audiences. In the general case, the aud value is an // array of case sensitive strings. In the common special case
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Fri Aug 29 02:39:48 GMT 2025 - 8.4K bytes - Click Count (0) -
docs/de/docs/advanced/security/http-basic-auth.md
# HTTP Basic Auth { #http-basic-auth } Für die einfachsten Fälle können Sie <abbr title="HTTP-Basisauthentifizierung">HTTP Basic Auth</abbr> verwenden. Bei HTTP Basic Auth erwartet die Anwendung einen Header, der einen Benutzernamen und ein Passwort enthält. Wenn sie diesen nicht empfängt, gibt sie den HTTP-Error 401 „Unauthorized“ zurück.Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Sat Sep 20 15:10:09 GMT 2025 - 6.2K bytes - Click Count (0) -
docs/es/docs/advanced/security/http-basic-auth.md
# HTTP Basic Auth { #http-basic-auth } Para los casos más simples, puedes usar HTTP Basic Auth. En HTTP Basic Auth, la aplicación espera un header que contiene un nombre de usuario y una contraseña. Si no lo recibe, devuelve un error HTTP 401 "Unauthorized". Y devuelve un header `WWW-Authenticate` con un valor de `Basic`, y un parámetro `realm` opcional. Eso le dice al navegador que muestre el prompt integrado para un nombre de usuario y contraseña.Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Tue Dec 16 16:33:45 GMT 2025 - 5.4K bytes - Click Count (0) -
cmd/sts-datatypes.go
type LDAPIdentityResult struct { Credentials auth.Credentials `xml:",omitempty"` } // AssumeRoleWithCertificateResponse contains the result of // a successful AssumeRoleWithCertificate request. type AssumeRoleWithCertificateResponse struct { XMLName xml.Name `xml:"https://sts.amazonaws.com/doc/2011-06-15/ AssumeRoleWithCertificateResponse" json:"-"` Result struct { Credentials auth.Credentials `xml:"Credentials,omitempty"`Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Fri May 27 00:58:09 GMT 2022 - 9.9K bytes - Click Count (0) -
CHANGELOG/CHANGELOG-1.24.md
**Note**: This only impacts the cluster if the ServiceAccount admission plugin is used (most cluster should have this on by default as recommended in https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/#serviceaccount), the `kubernetes.io/enforce-mountable-secrets` annotation is used by a service account (this annotation is not added by default), and Pods are using ephemeral containers. **Affected Versions**:
Created: Fri Dec 26 09:05:12 GMT 2025 - Last Modified: Thu Aug 24 00:02:43 GMT 2023 - 473.4K bytes - Click Count (0) -
docs/en/docs/advanced/security/http-basic-auth.md
# HTTP Basic Auth { #http-basic-auth } For the simplest cases, you can use HTTP Basic Auth. In HTTP Basic Auth, the application expects a header that contains a username and a password. If it doesn't receive it, it returns an HTTP 401 "Unauthorized" error. And returns a header `WWW-Authenticate` with a value of `Basic`, and an optional `realm` parameter. That tells the browser to show the integrated prompt for a username and password.Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Sun Aug 31 09:15:41 GMT 2025 - 5K bytes - Click Count (0) -
docs/ru/docs/advanced/security/http-basic-auth.md
# HTTP Basic Auth { #http-basic-auth } Для самых простых случаев можно использовать HTTP Basic Auth. При HTTP Basic Auth приложение ожидает HTTP-заголовок, который содержит имя пользователя и пароль. Если его нет, возвращается ошибка HTTP 401 «Unauthorized». Также возвращается заголовок `WWW-Authenticate` со значением `Basic` и необязательным параметром `realm`. Это говорит браузеру показать встроенное окно запроса имени пользователя и пароля.Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Tue Sep 30 11:37:11 GMT 2025 - 7.4K bytes - Click Count (0)