- Sort Score
- Result 10 results
- Languages All
Results 11 - 20 of 58 for isImplicit (0.05 sec)
-
guava/src/com/google/common/graph/EdgesConnecting.java
import com.google.common.collect.UnmodifiableIterator; import java.util.AbstractSet; import java.util.Map; import org.jspecify.annotations.Nullable; /** * A class to represent the set of edges connecting an (implicit) origin node to a target node. * * <p>The {@link #nodeToOutEdge} map means this class only works on networks without parallel edges. * See {@link MultiEdgesConnecting} for a class that works with parallel edges. *
Registered: Fri Dec 26 12:43:10 UTC 2025 - Last Modified: Mon Aug 11 19:31:30 UTC 2025 - 2.1K bytes - Viewed (0) -
okhttp-tls/src/main/kotlin/okhttp3/tls/internal/der/CertificateAdapters.kt
* validity Validity, * subject Name, * subjectPublicKeyInfo SubjectPublicKeyInfo, * issuerUniqueID [1] IMPLICIT UniqueIdentifier OPTIONAL, -- If present, version MUST be v2 or v3 * subjectUniqueID [2] IMPLICIT UniqueIdentifier OPTIONAL, -- If present, version MUST be v2 or v3 * extensions [3] EXPLICIT Extensions OPTIONAL -- If present, version MUST be v3 * } * ```
Registered: Fri Dec 26 11:42:13 UTC 2025 - Last Modified: Wed Mar 19 19:25:20 UTC 2025 - 13.6K bytes - Viewed (0) -
build-logic-commons/publishing/src/main/kotlin/gradlebuild.publish-public-libraries.gradle.kts
// Otherwise we get // ask ':tooling-api:publishGradleDistributionPublicationToRemoteRepository' uses this output of task ':tooling-api:signLocalPublication' // without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. tasks.named("publishGradleDistributionPublicationToRemoteRepository") {Registered: Wed Dec 31 11:36:14 UTC 2025 - Last Modified: Thu Oct 30 16:56:31 UTC 2025 - 5.7K bytes - Viewed (0) -
docs/sts/dex.yaml
# Options for controlling the logger. logger: level: "debug" format: "text" # can also be "json" # Default values shown below oauth2: # use ["code", "token", "id_token"] to enable implicit flow for web-only clients responseTypes: [ "code", "token", "id_token" ] # also allowed are "token" and "id_token" # By default, Dex will ask for approval to share data with applicationRegistered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Wed Jul 15 11:55:55 UTC 2020 - 2.7K bytes - Viewed (0) -
docs/uk/docs/tutorial/security/index.md
* Деякі з цих потоків підходять для створення власного провайдера автентифікації OAuth 2.0 (наприклад, Google, Facebook, X (Twitter), GitHub тощо): * `implicit`— неявний * `clientCredentials`— облікові дані клієнта * `authorizationCode` — код авторизації * Але є один окремий «потік», який ідеально підходить для реалізації автентифікації всередині одного додатку:Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Tue Jun 24 18:57:48 UTC 2025 - 6.8K bytes - Viewed (0) -
build-logic/binary-compatibility/src/test/groovy/gradlebuild/binarycompatibility/PublicAPIRulesTest.groovy
public interface Inner { } } """ then: rule.maybeViolation(jApiInnerClass) == null } def "the @since annotation on implicit enum method '#implicitMethod#paramTypes' is not required"() { given: def rule = withContext(new SinceAnnotationRule([:])) def jApiMethod = Stub(JApiMethod) jApiMethod.name >> implicitMethodRegistered: Wed Dec 31 11:36:14 UTC 2025 - Last Modified: Fri Jun 06 17:52:09 UTC 2025 - 16K bytes - Viewed (0) -
docs/ru/docs/advanced/security/oauth2-scopes.md
Самый распространённый — «implicit flow». Самый безопасный — «code flow», но он сложнее в реализации, так как требует больше шагов. Из‑за сложности многие провайдеры в итоге рекомендуют «implicit flow». /// note | Примечание Часто каждый провайдер аутентификации называет свои «flows» по‑разному — как часть бренда.
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Tue Sep 30 11:37:11 UTC 2025 - 20.7K bytes - Viewed (0) -
docs/de/docs/tutorial/security/index.md
* `oauth2`: Alle OAuth2-Methoden zum Umgang mit Sicherheit (genannt „Flows“). * Mehrere dieser Flows eignen sich zum Aufbau eines OAuth 2.0-Authentifizierungsanbieters (wie Google, Facebook, X (Twitter), GitHub usw.): * `implicit` * `clientCredentials` * `authorizationCode` * Es gibt jedoch einen bestimmten „Flow“, der perfekt für die direkte Abwicklung der Authentifizierung in derselben Anwendung verwendet werden kann:
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Sat Sep 20 15:10:09 UTC 2025 - 5.2K bytes - Viewed (0) -
docs/en/docs/tutorial/security/index.md
* `oauth2`: all the OAuth2 ways to handle security (called "flows"). * Several of these flows are appropriate for building an OAuth 2.0 authentication provider (like Google, Facebook, X (Twitter), GitHub, etc): * `implicit` * `clientCredentials` * `authorizationCode` * But there is one specific "flow" that can be perfectly used for handling authentication in the same application directly:
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Sun Aug 31 10:49:48 UTC 2025 - 4.4K bytes - Viewed (0) -
docs/pt/docs/tutorial/security/index.md
* `oauth2`: todas as formas do OAuth2 para lidar com segurança (chamados "fluxos"). * Vários desses fluxos são apropriados para construir um provedor de autenticação OAuth2 (como Google, Facebook, X (Twitter), GitHub, etc): * `implicit` * `clientCredentials` * `authorizationCode` * Mas existe um “fluxo” específico que pode ser perfeitamente usado para resolver autenticação diretamente na mesma aplicação:
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Dec 17 10:17:03 UTC 2025 - 4.9K bytes - Viewed (0)