The Wayback Machine - https://web.archive.org/web/20220606121706/https://github.com/topics/authorization
Skip to content
#

authorization

Here are 2,660 public repositories matching this topic...

Sa-Token

这可能是史上功能最全的Java权限认证框架!目前已集成——登录认证、权限认证、分布式Session会话、微服务网关鉴权、单点登录、OAuth2.0、踢人下线、Redis集成、前后台分离、记住我模式、模拟他人账号、临时身份切换、账号封禁、多账号认证体系、注解式鉴权、路由拦截式鉴权、花式token生成、自动续签、同端互斥登录、会话治理、密码加密、jwt集成、Spring集成、WebFlux集成...

  • Updated May 22, 2022
  • Java
TheLunaticScripter
TheLunaticScripter commented May 31, 2022

Currently when the sdk is called and the decision is sent to a decision log server each opa call looks like a new OPA. Adding an id would allow the user of the SDK to use the same id even if there are multiple calls.

What part of OPA would you like to see improved?

SDK

Describe the ideal solution

When calling the sdk the user can specify an opa id.

Describe a "Good Enough" solu

oso
ximon18
ximon18 commented Mar 18, 2021

With oso 0.11.1 and Rust client code.

When tracking down policy logic failures using the POLAR_LOG=1 environment variable I will see the logging of the execution of all of my inline queries. The problem is that I have lots of these, but usually I'm not interested in the ones in my core policy files which are fairly static and unchanging, but rather I'm interested in those policy sources that

good first issue

Improve this page

Add a description, image, and links to the authorization topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the authorization topic, visit your repo's landing page and select "manage topics."

Learn more