Anton

@adedov
2 Followers
7 Following
3 Posts

Выступил на митапе по аутентификации/авторизации, который организовал коллега и "свободный художник" в сфере IAM (см https://t.me/unauthz):

https://youtu.be/wMMbIx0d1us

#iam #authz #rbac #abac

401 Unauthorized: аутентификация и не только

Канал про IAM и все, что рядом: - аутентификация - session management - access control Возможны также посты про API и InfoSec Чат: @unauthz401 Автор: @andreukuznetsov

Telegram
Usual #RBAC, #ABAC policies express rules presuming that an actor who initiated a request is a single principal. Is there an approach that allows requests w/ composite tokens containing at least two principals? Take into account own privileges of an oauth client and a user.

@mortal @jgayfer A client that cannot securely store its secret is titled public. For example CLI and mobile apps are usually public ones. For instance, secret of a Google cloud CLI is a publicly known string.

There are methods that allow public clients to mitigate some risks related to the fact that their secret is public. For example DPoP allows one to bind access and refresh tokens to a specific private key that could be stored on a specific device (bind user authorization to the device).