I have read this article which talks about adding custom field (email confirmation for 2nd time) in the Self Registration page. The scenario is simple:
To add field Confirm Email for 2nd time in the Self Registration page. This behavior can been seen in many of the websites. So, what would you do when you are using OIM for this purpose? By default, OIM supports adding custom fields to custom self registration page by modifying the FormMetaData.xml file. However, the problem arises when you want to add logic to the form to have the Email confirm field match the Email field. This can be done easily (either by adding javascript or by adding custom code) if it is a custom Self Registration Page and not OIM self registration page. The workaround is so simple: Decompile the tcSelfRegistrationAction.class java file deployed in the XellerateFull.ear file and copy the function of confirming the password and change the field name to email.
I am engulfed in Identity & Access Management space. I have expertise in providing the optimized solutions for user provisioning, web access management, Single Sign-On and federation capabilities etc., for on-prem and cloud deployments. I am here to share troubleshooting tips, discuss architecture and design aspects, integration scenarios and many more that I have experienced with.
Monday, November 8, 2010
Sunday, November 7, 2010
Identity propogation in a flow involving OAM, OWSM and OSB
I have recently gone through this article and found very interesting.
The scenario is this:
OAM is protecting a Portal UI application which is making WebService calls. WebService is protected by OWSM and the communication is made through OSB. Two approaches were discussed in detail in that article.
The scenario is this:
OAM is protecting a Portal UI application which is making WebService calls. WebService is protected by OWSM and the communication is made through OSB. Two approaches were discussed in detail in that article.
Subscribe to:
Posts (Atom)