Difference between revisions of "Creating authentication registration for external users"

From PegaWiki
Jump to navigation Jump to search
(final curator review)
Tag: Visual edit
(added owner)
Tag: Visual edit
Line 5: Line 5:
 
|Applications=Platform
 
|Applications=Platform
 
|Capability Area=Security
 
|Capability Area=Security
|Owner=
+
|Owner=Marty Guyote
 
}}
 
}}
  

Revision as of 20:29, 8 September 2020

Best practices for creating authentication registration for external users

Description Best practices for creating authentication registration for external users
Version as of 8.4
Application Platform
Capability/Industry Area Security



The following are best practices to follow for authentication and registration of external users in public-facing applications (that is, applications whose operators are not client’s own employees). Users of such an application may be initially anonymous (identity unknown), and may have very restricted access to application features. They may then register themselves or have their identity verified partway through a session, and the session should continue transparently, with their operator context appropriately updated and with expanded privileges.

A common example is an online shopping site, in which unauthenticated users can browse and add items to a shopping cart, and then they either create an account or enter their credentials to check out.

Our best practices for this question are captured in the Community article listed below. The guidance is as follows:

  • Use the out-of-the-box Authentication Service rule of the Anonymous type for authentication. In that rule, specify an access group with the appropriate extremely-limited privileges that should be sufficient for an anonymous user. The privileges would usually ensure that such users can only use the case types required for them to create their cases, can only access data they have created themselves, and have no access to other application functionality, such as reporting, etc.
  • Once an end user is authenticated with a known identity, use the Re-Authentication gadget to change their context and access group info, rather than writing custom code.
  • In public-facing applications where end users do not need access to information about other operators, we recommend that you restrict all access to data in the Data-Admin-OperatorID class to only the end user’s data through an access control policy. You can do this by enabling the out-of-the-box rules pyDefault and pyRestrictToSelf in the Data-Admin-OperatorID class.

For more information, see the following articles on Pega Community: