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.
4D Netkit: Enhancement of OAuth2 Authorization
With 4D v19 R3, connecting your application to the Microsoft Graph API through OAuth 2.0 has become incredibly convenient using 4D NetKit.
Now, with 4D v20 R2, you can seamlessly obtain an OAuth 2.0 token for Google API or other OAuth 2.0 servers. And even better, to further enhance the integration of this authentication process into your application, we have introduced a feature that allows you to display your HTML page directly in your web browser once the token is received.
Keep reading for all the details!
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!