Enrollment via Unauthenticated Extension

Question

What is the best way these days to enroll a user using an unauthenticated extension? Is it via the Caliper API? I know at one point it wasn't recommended to have an extension use the Caliper API due to the network routing / firewall changes to accomodate that as opposed to using the Caliper API source code that uses enrolled_entity and whatnot. However, the benefit to using the Caliper API is that it encapsulates and abstracts the enrollment details so that if changes/fixes in the enrollment logic need to be introduced by Q2, it can be done in one place and leveraged automatically by anyone using it.

		
				0
				
Posted 
	one year ago

					⠿More
				  		
			 Report
		
					Mark Coburn
				
					10

Andrew Yeager · Answer

Great question Mark It sparked some good conversation within the Q2 team The only hesitation with saying The Caliper API is due to the network effect you mentioned However we don t really like making you recreate all the steps that enrollment endpoint on the API covers for you either for all the reasons you mentioned Use the Caliper API endpoint at this time and perhaps we will begin making a workflow object that could be utilized by both the API and our SDK users without the additional network requirement

Answers