SOM Web Form Matching
Originally Published: 2007-03-12
Article Number
Applies To
Issue
Resolution
NOTE: I have had problems with any tag that has parameters like <html mlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
First you must learn a web page using the Application Learning Wizard. After your SOM client has synchronized with the server, take a look in your aelist.ini (under %userprofile%\Application Data\passlogix).
In there you will see a entry like [My web app] with a bunch of settings after it.
If your login page had the text "Please login" you could do the following:
Grab the aelist.ini entry mentioned above, then login to your SOM Server admin ui, then change the URL to have the override page which is also listed above.
Select the SSO policy that you want to apply the override to, and enter the following:
[My web app]
Match1=ManuallyDefinedWebMatchMyWebApp
[ManuallyDefinedWebMatchMyWebApp]
Match1=all,body,text,substr,Please login
This will add the Match1 line to the My web app section, and create a new section defining the match. The label ManuallyDefinedWebMatchMyWebApp is something random I just thought up. This can be anything, passlogix uses what appears to be large random numbers to label their matches. I suggest using something intelligible, this way if you visit your override screen, you will understand what the override is, and why it is there.
This override is one that programmed into Passlogix, then took a look into their aelist.ini to see what the Match line looked like.
I have since re-used this one line, only changing the text at the end to match the text on a given web page.
This match can be used in 2 ways. It can be used to uniquely identify a web page for login, or it can be used to uniquely identify a web page that you want to disable (for instance a logoff page to prevent looping).
A technical breakdown of the Match line:
All = means it scans for any occurrence of the following html tag
body = this is the html tag that it is searching within, so there has to be a <body> and a </body> for this to work
text = this means it is doing a text match (vs doing an html match)
substr = this means it only has to match a part of the string (otherwise you would have to have the whole body in the line)
Please login = this is the exact text that exists in the web pages source that SSO looks for
In SOM 4.7 there should be a Server UI that allows for defining a web form match, which should render this manual process obsolete. If you have any questions, or suggestions on making this solution better, please let me know.
Notes
INTERNAL Solution ONLY
Related Articles
RSA Token Client (RTS) DLL not rotating its log file Number of Views How to recreate a PKCS#12 and/or to change PKCS#12 password? Number of Views Security Object Manager (SOM) client fails to connect to SOM Server Number of Views RSA Federated Identity Manager (FIM) services do not start after changing hardware (upgrading RAM etc.) to the machine ru… Number of Views Can a certificate be imported onto SID800 using RSA Smart Card Middleware 3.0 ? Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.9 Release Notes (January 2026) An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x RSA Authentication Manager 8.8 Setup and Configuration Guide
Don't see what you're looking for?
