4D NetKit: Secure OpenID Authentication with nonce attribute
When working with modern authentication flows, security is paramount. Developers often need to integrate authentication with trusted identity providers such as Google or Microsoft. This is where OpenID Connect (OIDC) comes into play.
OIDC is an identity layer built on top of OAuth 2.0. It allows your application to verify the identity of a user and to obtain basic profile information in a secure way. Starting with the latest enhancements to the cs.NetKit.OAuth2Provider class, 4D 21 now makes it easier to work with OpenID Connect by supporting the nonce parameter, along with new token attributes, including the id_token.
4D NetKit: Simplifying OAuth 2.0 Redirects after authentication
4D NetKit just made redirecting users after OAuth 2.0 authentication easier with 4D 21. The OAuth2Provider class in 4D NetKit now allows real URLs for authenticationPage and authenticationErrorPage. This means you now have more redirection options after authentication, like a Qodly pages or HTTP Handlers. Whether the authentication succeeds or fails, you stay in control of the user experience with smooth, flexible redirection options.
4D NetKit: Use your web server host ports to retrieve your OAuth 2.0 authentication response
When using OAuth 2.0 authentication with 4D NetKit, you must define a redirect URI to indicate where the OAuth 2.0 server should return the authentication result. With 4D 20 R9, you can now use your host web server’s address and ports to retrieve your authentication responses. This enhancement streamlines the authentication process, prevents port conflicts, and improves security.
4D Netkit: Customizing OAuth 2.0 Connection Interface
Some of you may need to manage the display of the connection interface during an OAuth 2.0 connection for design or technical reasons. From 4D 20 R6, you can choose not to automatically open a web browser to display the connection interface but use the authenticateURI to display it where you like.
In this blog post, we’ll walk through an example of opening the Microsoft login interface within a web area.
4D NetKit: PKCE for OAuth 2.0
OAuth 2.0 is a cornerstone of modern authentication. Enter PKCE, a pivotal enhancement fortifying OAuth 2.0 against interception and replay attacks. With the introduction of the 4D 20 R5, we now offer seamless integration of PKCE into OAuth 2.0 authentication processes.
Connect your mail transporters with an OAuth 2.0 token
Lately, email servers on the web have started to move to OAuth 2.0 authentication to increase security. Starting with 4D v18 R6, 4D provides a way to set the OAuth 2.0 authentication mode of a connection. Keep reading for the details!
Contact us
Got a question, suggestion or just want to get in touch with the 4D bloggers? Drop us a line!
* Your privacy is very important to us. Please click here to view our Policy