Friendly OAuth2 Server
Sign Up Sign In
Index Documentation Download Check license
Friendly oAuth2 server documentation
Friendly oAuth2 server documentation
Setup and running
Setup and running test version
Setup and running production version
Setup https protocol
Setup other database
Working with OAuth2 and OpenId Methods
OAuth2
OAuth2 code flow
OAuth2 implicit flow
OAuth2 user password flow
OAuth2 client credential flow
OAuth2 refresh token flow
OpenId
OpenId code flow
OpenId implicit flow
Client secret authentication
Client secret basic
Client secret post
Client secret jwt
Client key jwt
None
Extra
OAuth2 dynamic registration
OAuth2 revoke
OAuth2 introspect
OAuth2 jwks.json
OAuth2 .well-known
OAuth2 backchannel_logout
OAuth2 userinfo
Extra settings
Control panel
User section
User sessions 1
User sessions 2
User info
Change password
Delete account
Client section
List of registered clients
Number of authorizations per day
New client registration
Admin section
Client authorizations
Auth settings
Users
Clients
Administrators
Roles
Limits
Create user
Limits
On this page you can set restrictions separately for users and separately for client applications. For users, set the maximum number of valid codes as few as possible. The maximum number of valid tokens is the number of user logins multiplied by the number of client applications through which the user was authorized. It is advisable for clients to set the token validity to the same value, because the standard OAuth2 libraries for client applications will only recognize the validity of the access token. If your application is used in a small enterprise, then the value of the maximum number of valid tokens = 10,000 is quite enough. If you have a massive use case, then it is advisable to increase the value to 2 * number of client applications * number of users or up to the throughput of your cluster.
Friendly OAuth2 Server
prodmicroservice.com
2024