Skip to Main Content
Feature Request FR-2598
Product Area Security
Status CLOSED

22 Voters

Persistent Authentication for Social sign-in

pmushkov Public · Jun 23 2022

Idea Summary
Enable persistent authentication for 3rd party authentication providers such as Google, Azure, OKTA, etc.

Use Case
The number of applications using the Social sign-in for authenticating their users is growing rapidly. What's more, with the PWA becoming available, there are many applications that would need the Native application experience. Which includes opening the application without the need to authenticate every time. 

Preferred Solution (Optional)
Although the technical solution might not be easy, I think it's worth investing time, as this will be one of the must-have features for the future of mobile APEX apps.

We reviewed this idea carefully, and while it was interesting, we concluded that due to all the internal implications we need to take into account, it is not feasible in APEX.

Known Duplicates

Known duplicates

FR-2729
FR-2729 Enable persistent authentication when using Apex Social Authentication (google/facebook etc) via OAuth

Comments

Comments

  • vincent morneau Admin OP 2.9 years ago

    Hi Plamen,

    Given how APEX handles with the persistent authentication token upon APEX login process, APEX can't safely delegate the responsibility to the 3rd party provider. It should be up to the provider to automatically reauthenticate the user. We discussed this idea and decided that it is likely not feasible.