K2 SmartObject OAuth Authentication – Prevent First-Time Redirect to Authorize URL (Consent Prompt) – K2 5.4 FP23

It depends. The need for a consent prompt during the user flow is handled by your configured IdP (Identity Provider such as Entra ID).

With user flow, the first time a user logs into your application and attempts to take some sort of action that requires to use of a smart object configured with OAuth, the user will be presented with a authentication prompt so that K2 can request and cache that user’s OAuth Token. So it will always happen at least once.

If as part of that flow, the user is asked to consent to K2 accessing or having some sort of right as part of the authentication process, then that is a configuration issue on the part of the IdP. You would need to review the app registration for K2 in your environment with that particular IdP.

K2 itself does not control that flow; it merely presents the prompts for each step dictated by the IdP.

Thank you for your explanation.

In our scenario, K2 SmartForms is using Forms Authentication, while the SmartObject Authentication Mode is configured as OAuth.

Is it possible to configure the SmartObject to connect to the OAuth API using an app-to-app (client credentials), server-to-server flow, or by specifying a dedicated service account instead?

Our goal is to avoid prompting end users for consent, since they are already authenticated via Forms Authentication in SmartForms. We would prefer not to require users to click the consent screen when executing the SmartObject.

Could you please advise whether this approach is supported and what configuration would be required on the IdP and K2 side?