- Sort Score
- Result 10 results
- Languages All
Results 61 - 67 of 67 for accessToken (0.16 sec)
-
docs/pt/docs/tutorial/security/simple-oauth2.md
A resposta do endpoint `token` deve ser um objeto JSON. Deve ter um `token_type`. No nosso caso, como estamos usando tokens "Bearer", o tipo de token deve ser "`bearer`". E deve ter um `access_token`, com uma string contendo nosso token de acesso. Para este exemplo simples, seremos completamente inseguros e retornaremos o mesmo `username` do token. /// tip | Dica
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Nov 12 16:23:57 UTC 2025 - 10.3K bytes - Viewed (0) -
.github/workflows/ci.yml
- name: 'Cancel previous runs' uses: styfle/cancel-workflow-action@85880fa0301c86cca9da44039ee3bb12d3bedbfa # 0.12.1 with: access_token: ${{ github.token }} - name: 'Check out repository' uses: actions/checkout@1af3b93b6815bc44a9784bd300feb67ff0d1eeb3 # v6.0.0
Registered: Fri Dec 26 12:43:10 UTC 2025 - Last Modified: Mon Dec 01 19:32:55 UTC 2025 - 4.7K bytes - Viewed (0) -
docs/zh/docs/tutorial/security/simple-oauth2.md
返回内容还应包含 `access_token` 字段,它是包含权限 Token 的字符串。 本例只是简单的演示,返回的 Token 就是 `username`,但这种方式极不安全。 /// tip | 提示 下一章介绍使用哈希密码和 <abbr title="JSON Web Tokens">JWT</abbr> Token 的真正安全机制。 但现在,仅关注所需的特定细节。 /// {* ../../docs_src/security/tutorial003.py hl[85] *} /// tip | 提示 按规范的要求,应像本示例一样,返回带有 `access_token` 和 `token_type` 的 JSON 对象。
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Mon Nov 18 02:25:44 UTC 2024 - 8.6K bytes - Viewed (0) -
docs/ko/docs/tutorial/security/simple-oauth2.md
그리고 액세스 토큰을 포함하는 문자열과 함께 `access_token`이 있어야 합니다. 이 간단한 예제에서는 완전히 안전하지 않고, 동일한 `username`을 토큰으로 반환합니다. /// tip | 팁 다음 장에서는 패스워드 해싱 및 <abbr title="JSON Web Tokens">JWT</abbr> 토큰을 사용하여 실제 보안 구현을 볼 수 있습니다. 하지만 지금은 필요한 세부 정보에 집중하겠습니다. /// {* ../../docs_src/security/tutorial003.py hl[85] *} /// tip | 팁 사양에 따라 이 예제와 동일하게 `access_token` 및 `token_type`이 포함된 JSON을 반환해야 합니다.
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Sat Feb 15 11:19:12 UTC 2025 - 10.8K bytes - Viewed (0) -
docs/sts/keycloak.md
-d "grant_type=client_credentials" \ "http://localhost:8080/auth/realms/{realm}/protocol/openid-connect/token" ``` The result will be a JSON document. To invoke the API you need to extract the value of the access_token property. You can then invoke the API by including the value in the Authorization header of requests to the API. The following example shows how to get the details of the user with `{userid}` from `{realm}` realm: ```Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Tue Aug 12 18:20:36 UTC 2025 - 8.1K bytes - Viewed (0) -
docs/sts/web-identity.md
| Params | Value | | :-- | :-- | | *Type* | *String* | | *Required* | *No* | ### RoleArn
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Tue Aug 12 18:20:36 UTC 2025 - 18.9K bytes - Viewed (0) -
src/main/java/org/codelibs/fess/opensearch/config/cbean/cq/bs/BsAccessTokenCQ.java
// ============= @Override public String asTableDbName() { return "access_token"; } @Override public String xgetAliasName() { return "access_token"; } // ===================================================================================Registered: Sat Dec 20 09:19:18 UTC 2025 - Last Modified: Sat Mar 15 06:53:53 UTC 2025 - 71.8K bytes - Viewed (0)