Gary,
Wow. From two sentence to several paragraphs. :) Now I also think I
have a better understand of what your attempting to do.
RE:
"
I cannot use the ^ because it is a password, and the user HAS to have
A-z and 0-9 as well.
"
Actually I think that is not true...
A Run if Like...
'New Password' LIKE (((( "%" + "[^A-z,0-9]" ) + "%" ) +
"[^A-z,0-9]" ) + "%" )
Should tell you if the field has at least two characters that are not
in those sets. (And the string can have values that are in those sets
anywhere in the LIKE match where a "%" exists.)
However... at the end of the day..
I think that building ARS workflow to do this kind of complex
pattern matching is likely a loosing battle. I would advocate the idea
of using an ARS Filter Plugin (Maybe even the Java Scripting Plugin)
for this kind of activity. You can actually use Regular expressions
and the code can validate multiple matches and return multiple returns
all in one call to the Plugin Server. Sure it requires more than "just
ARS knowledge" to do it, but there should be some standard-ish things
out there for password complexity checking in most languages.
(Especially C, Java, Perl, ....) [ I really like to reuse this kind of
stuff when ever possible. ]
I also have to note that v7.1 brings a new spin on all of this
stuff too. ( More built in features for local password management.) So
I am not sure how all of that works just yet as far as password
patterns etc... [ So, just some food for thought about what the future
might change and effect the stuff your building today. ]
--
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)
Love, then teach
Solution = People + Process + Tools
Fast, Accurate, Cheap.... Pick two.
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"
