What are the best practices to follow when one is customizing the smpwservices.fcc?
The default page while it does a good job of providing a base sample, I find writing hundreds of document.write methods to inject HTML customizations to be cumbersome.
What other methods have you used to make this cleaner and easier to maintain?
One commonly used approach is doing redirection from the smpwservices.fcc page based on the value for smauthreason
//Auth reason 19 - Account disabled due to inactivity
if ($$smauthreason$$ == 19)
//Redirect to InactiveAccount.html
//Auth Reason 24 - Account disabled due to excess Login
else if ( ($$smauthreason$$ == 24)
Hope this helps.
If you are fluent in JSP / Java or ASP - we can move all of that code into JSP or ASP and have the URL changes in the Password policy to redirect to your JSP / ASP page.
smpwservices.fcc provides you a base structure to begin working with user experience i.e. a demo. You'll need to tie in your JSP / ASP page to work with FCC (Same logic as Login.jsp posting to login.fcc) for some password journey's e.g. change password.
I just wanted to add other consideration :
You'll find tips about some customization to be put in
the smpwservices.fcc :
You might also rely on best practices about document.write methods.
There are many website on internet that discuss this too. This will give
you guide lines.
Consider to run the latest version of Web Agent with the latest out of the box
smpwservices.fcc, only to modify the lines that shows text, images and logo. Modify
as less as possible the other functions in order to preserve the out of the box security
of the smpwservice.fcc.
Hope that helps,