Overriding Web Server Properties in the PIA
<%=146%> meta-tag is directly in between other HTML tags, I can override this variable with a custom script that will perform the customizations to the sign in page. This allows me to easily (ab)use property #146 as a built-in hook that will allow for a tailored sign in page that is customization-free.
Managing custom property #146 via the text.properties file is undesirable as I want the ability to change the injected script without having to have access to the web server file system. Fortunately, we are able to use the Custom Properties tab on the Web Profile Configuration page in the PIA to override the value for property #146. We do not need to worry about the value defined in the text.properties file as the value specified on the web profile will take precedence. You will simply need to set the Property Name to 146, Validation Type to String and Property Value to the custom script to modify the signin.html page. As you can see from the picture below, you can append the script to the desired footer text so that you do not lose out on the message from getting displayed at the bottom of the sign in page.
Here is how the sign in page looks from storing the above fragment in the web profile custom property:
I freaking love this!
Right on! This is a nifty trick for sure :)
Hi Colton, This is a great article on the practical usage of custom web profile properties. Thank you.
I am just wondering if we can maintain multilingual content using these custom web profile properties. Because there are situations where we display different language verbiages on the signin page. Any thought on it?
Colton - This is amazing! Well done. Thank you for uncovering this hidden gem for the community!
Very informative, great way to do the customization to the login page.
Did this for the current project I am on and we did run into a few things, when we removed the background as they wanted white, the text and the borders on the text boxes were all wrong, created a little JS function to alter the CSS on the fly (10 different CSS styles needed changes) and it worked like a charm.
I also added some additional code to handle the branding of the timeout page as well with the same script.
Thank you for the feedback. I am glad this worked out for you.
Leave a comment
Your email address will not be published. Required fields are marked *