IOServer OIDC FAQs

Question 1

What is IOServer OIDC?

Accepted Answer

IOServer OIDC is an authentication middleware designed for the IOServer framework. It enables secure access to both Fastify HTTP routes and Socket.IO namespaces by integrating OpenID Connect (OIDC) and OAuth2 JSON Web Token (JWT) authentication.

Question 2

How does IOServer OIDC enhance application security?

Accepted Answer

It significantly boosts security by verifying JWT access tokens via remote JWKS, eliminating the need for secret storage on your application server. It also validates critical token claims like 'iss', 'aud', and expiry, while automatically provisioning user records for robust access control.

Question 3

Does IOServer OIDC support both HTTP and WebSocket authentication?

Accepted Answer

Yes, it provides dedicated middleware for both Fastify HTTP routes (`OidcHttpMiddleware`) and Socket.IO namespaces (`OidcSocketMiddleware`), ensuring comprehensive authentication across all layers of your IOServer application.

Question 4

What user context is available after successful authentication?

Accepted Answer

Upon successful authentication, IOServer OIDC injects a rich set of user context properties into requests and sockets. This includes `userId`, `userRole`, `roles`, `permissions`, `sub`, `email`, and `features`, making it easy for your handlers to implement granular access logic.

Question 5

Is secret storage required on the application server with IOServer OIDC?

Accepted Answer

No, a key security benefit of IOServer OIDC is that it requires zero secret storage on the application side. It securely verifies JWT signatures using public keys retrieved from a remote JSON Web Key Set (JWKS) endpoint, simplifying deployment and enhancing security.

IOServer OIDC

IOServer OIDC

주요 기능

사용 사례

주요 기능

사용 사례