Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Content Management (Extended ECM)
CSIDE and OScript
Password expiration and redirection of user
Chris_Bowman_(spawaruser1_-_(deleted))
We are running LL95 and are expiring passwords every 90 days. We have a cusotm module that is used for registration and managing user accounts/groups. When the user changes his/her password we would like to redirect them to a custom RH to update personal information.I traced the RH and html pages and found that lleditexpiredpw.html is displayed when a users password has expired. When the user submits a new password the RH SaveExpiredPWChange is called, the new password is checked/saved and the user is then redirected to the Enterprise page.Will the following work?Inside lleditexpiredpw.html:1)create a new input called original_nextURl and set it equal to what nextURL would be set.2)set nextURL to the RH for our custom moduleInside cusotm RH:3)redirect the user to the orginal_nextURL
Find more posts tagged with
Comments
Hans Stoop
Message from Hans Stoop via eLinkThat should work.Another method, used in other places, is to set the new nextURL to &nexturl=.Changing webLingo files is not well supported. Upgrades are difficultand only one module can change a webLingo. At least you should use oneof the HTMLmapping utilities, so you don't need to alter originalLivelink files directly.Personally I would use the wrapper functionality in customizationsRT, towrap around the SaveExpiredPWChange.Execute function and change, beforecalling the original execute, the nextURL in the args to &nexturl=.Hans > -----Original Message-----> From: eLink Discussion: Livelink Builder Discussion > [mailto:componentbuilder@elinkkc.opentext.com] > Sent: vrijdag 3 februari 2006 21:55> To: eLink Recipient> Subject: Password expiration and redirection of user> > Password expiration and redirection of user> Posted by Bowman, Chris on 02/03/2006 03:50 PM> > We are running LL95 and are expiring passwords every 90 days. > We have a cusotm module that is used for registration and > managing user accounts/groups. When the user changes his/her > password we would like to redirect them to a custom RH to > update personal information.> > I traced the RH and html pages and found that > lleditexpiredpw.html is displayed when a users password has > expired. When the user submits a new password the RH > SaveExpiredPWChange is called, the new password is > checked/saved and the user is then redirected to the Enterprise page.> > Will the following work?> > Inside lleditexpiredpw.html:> 1)create a new input called original_nextURl and set it equal > to what nextURL would be set.> > 2)set nextURL to the RH for our custom module> > Inside cusotm RH:> 3)redirect the user to the orginal_nextURL> > [To reply to this thread, use your normal E-mail reply function.]> > ============================================================> > Discussion: Livelink Builder Discussion>
https://knowledge.opentext.com/knowledge/livelink.exe/open/765419>
; > Livelink Server:>
https://knowledge.opentext.com/knowledge/livelink.exe>
; > To Unsubscribe from this Discussion, send an e-mail to > unsubscribe.componentbuilder@elinkkc.opentext.com.> > >
Donna Nalls
Chris,Under normal circumstances, you are on the right track; unfortunately, it looks like the OT developer hard-coded the .fLocation feature in the SaveExpiredPWChange.Execute method:.fLocation = .URL() + "?func=ll.GetDefaultRH" which means no matter what you do in the html, once the form is submitted to SaveExpiredPWChange, the redirection will always be the user's default livelink location.So, in addition to your modifications to the lleditexpiredpw.html webLingo file, you will likely have to orphan SaveExpirePwChange RH and make a change to the redirection block of code.Best,Donnadnalls@wisteria-it.com
Chris_Bowman_(spawaruser1_-_(deleted))
I have written about 7 or 8 modules and I have a degree in programming so the OScript is foreign to me. I am familiar with .fLocation anmd should have seen that. I have seen references to the customizationsRT is other topics but never really paid much attention. Can you give me some more detials on this module? You mentioned HTMLmapping utilities. Can you give me some details on these utilities?If I were to orphan the SaveExpiredPWChange RH, where would I orphan it to? This would require the module to be rebuilt, saved, exported, etc. and then replaced on the production machine, correct?In the past we have always stayed away from modifing the LL code, other than making changes to the login/logout pages. But, this time it may become necessary because our customer now has a requirement to know more detailed information about it's user and this information is only accessed through our custom registration module.Thanks for your help.
Donna Nalls
Hi Chris,Hans is correct, that it is best to use the utility modules for overwriting core LL code. The HTMLMap module was developed by Martin Scott - who used to be a PS consultant and is now an OT developer (but not the one that didn't check for a nextUrl arg in the SaveExpiredPwChange). The module allows you to "map" core ll webLingo (HTML) files into a custom module....doing so means that you don't have to track all of these html files in their core directories when you go to do an upgrade...they are all in your custom module -- you still have to validate the code when you do an upgrade, you just don't have to remember they are all over the place. I will look for the module and send in another thread. Or, possibly Hans has it handy.I have not worked with the CustomizationsRT module - i'm sure Hans can give you some detail on it.Here is the most simple approach that i can offer you:1) orphan the SaveExpiredPwChange RH into your custom module (or create a new custom module for this task).2) change the .fFuncPrefix value from "ll" to something that indicates your custom module: i.e. "mycustomll"3) make your code changes to the redirection block4) modify the lleditexpiredpw.html file: a) change the "func" hidden input value to "mycustomll.SaveExpiredPwChange" b) manipulate your NextUrl and Original_NextUrl params as you were planning originally.Oh, don't forget to register your new request handler....Please let me know if you have any questions or need more detail....Best,Donnadnalls@wisteria-it.com703.421.1778
Chris_Bowman_(spawaruser1_-_(deleted))
Message from Chris Bowman via eLinkThanks Donna,I will have to look at it more next week.Thanks again,Chris-----Original Message-----From: eLink Discussion: Livelink Builder Discussion[mailto:componentbuilder@elinkkc.opentext.com] Sent: Friday, February 03, 2006 5:25 PMTo: eLink RecipientSubject: Hi Chris,Hi Chris,Posted by Nalls, Donna on 02/03/2006 06:22 PMHi Chris,Hans is correct, that it is best to use the utility modules for overwritingcore LL code. The HTMLMap module was developed by Martin Scott - who used to be a PSconsultant and is now an OT developer (but not the one that didn't check fora nextUrl arg in the SaveExpiredPwChange). The module allows you to "map"core ll webLingo (HTML) files into a custom module....doing so means thatyou don't have to track all of these html files in their core directorieswhen you go to do an upgrade...they are all in your custom module -- youstill have to validate the code when you do an upgrade, you just don't haveto remember they are all over the place. I will look for the module andsend in another thread. Or, possibly Hans has it handy.I have not worked with the CustomizationsRT module - i'm sure Hans can giveyou some detail on it.Here is the most simple approach that i can offer you:1) orphan the SaveExpiredPwChange RH into your custom module (or create anew custom module for this task).2) change the .fFuncPrefix value from "ll" to something that indicates yourcustom module: i.e. "mycustomll"3) make your code changes to the redirection block4) modify the lleditexpiredpw.html file: a) change the "func" hidden input value to"mycustomll.SaveExpiredPwChange" b) manipulate your NextUrl and Original_NextUrl params as you wereplanning originally.Oh, don't forget to register your new request handler....Please let me know if you have any questions or need more detail....Best,Donnadnalls@wisteria-it.com703.421.1778[To reply to this thread, use your normal E-mail reply function.]============================================================Topic: Password expiration and redirection of user
https://knowledge.opentext.com/knowledge/livelink.exe/open/4528262Discussion
: Livelink Builder Discussion
https://knowledge.opentext.com/knowledge/livelink.exe/open/765419Livelink
Server:
https://knowledge.opentext.com/knowledge/livelink.exeTo
Unsubscribe from this Discussion, send an e-mail tounsubscribe.componentbuilder@elinkkc.opentext.com.
Hans Stoop
Hi Chris,If SaveExpiredPWChange set the fLocation hard coded, you should changethe webLingo file, but only change the RH. It doesn't make sense tochange 2 parts of Livelink.I've attached a module that does the wrapping for you. I also includedcustomizationsRT. In the module you need to change the execute functionof 'Patched SaveExpiredPWChange' to what you need.Orphaning objects works in some (many) cases but not in all cases. Inthis case it will work. What you should do is creating your own module,orphan the SaveExpiredPWChange RH and make the changes you require. Theyou need to install the new module on the production system. But it maybe better to write a patch for it.The way to use the wrapper function I used in the module, is explainedin the documentation feature of the Patch orphan in the module and inthe attached index.html file.The customizationsRT module contains a lot of extensions to the builder,like wizzard for creating a module, removing breakpoints and make itready for delivery. See the tutorial section in the documentation fordetails.It also contains functions like the wrapping and HTMLmapping. WhatHTMLmapping does is that at runtime it let Livelink use a webLingo filein your own module in stead of a standard Livelink webLingo file. Thereare different versions of it available in customizationsRT, but the oneI always use is the one in which I have a mapping directory in mymodule. Then I can just add webLingo files to that directory if I wantto change the standard webLingo file. See MapModules in th esecondindex.html file for details.HansPS. Via the KC I can only add 1 attachment, so the other followes in other responses.
Hans Stoop
See attached
Hans Stoop
See attached
Hans Stoop
See attached
Donna Nalls
Hi Hans,My suggestion for changing both the RH and the webLingo was to give Chris' organization the flexibility to make future redirection changes in the webLingo file only. If he modifies the RH now in his custom module, then, if it needs to change in the future, whomever is responsible for the changes doesn't necessarily have to have SDK experience.Or, hopefully, someday the OT developer will go back and fix his/her code to handle the redirection, as it should have been handled in the first place. In that case, Chris' organization could back out the custom module and stick to his original thought of modifying the webLingo file.So, in that sense - it does make sense to change both.Great that you have all of these wonderful utilities and good advice -- but, there is no reason to criticize others that are also offering a solution.Regards,Donna
Rolf_Poser_(eu0018377_-_(deleted))
Could this version please be moved to the regular place?The version in the expected location is still v2.1.1?Thanks,Rolf.
