Hello, Since the last update from this Saturday, we've had problems with our portal visitor passwords. Some of the portal visitors, on all of our customers have had their password modified. Their password cannot be printed in views, view pages, and emails. it is printed as a 34 chars length : like "Zab4352bcfba31112977699ca38d65214". If we manually change the password, of if we change it by trigger, it changes the password to another 34 chars password. This is a major problem for us, some of our customers have reported that they couldn't connect to the portal anymore, and there is no way for us to give them back to them. The only way they can get their password back is by clicking the "forgot password" link. Any email that sends their password sends a 34 chars password. Can you correct this problem please? Thanks, Romain Pennes.
This is intended security update explained in documentation. After password reset it can be used in emails etc, but later on it will no longer be available for display.
What do you mean by "some of our customers have reported that they couldn't connect to the portal anymore" ? If they forgot password they should use "Forgot Password" link and reset it. Or do you mean that none of customers can login to portal?
Nevermind about the visitors that could not connect to the portal.
We have imported portal visitors monthes ago, and generated random passwords for all of them last week.
We would like to send to them their login and password for their first connection.
How can we do that?
Also, the password is encrypted in the emails, even after updating it from the platform.
Finally, what is the use of the "Show actual password on view pages and email templates" checkbox in the edit field screen, if it is encrypted when unchecked.
Thank you for helping us resolving this.
Romain Pennes.
You can set "password" field through trigger and send email, that should work.
Alright, it works when calling the "Send email trigger" when called with the 'rbv_api.runTrigger' function from the trigger setting the password.
It is not possible to manually call an action "Setting password" calling a trigger that sets the passwords.
And then manually call an action "Send login information" calling a trigger that sends the email.
We understand the security issue behind this.
I believe we can make it work this way.
Thanks a lot for your reaction and your work.
Romain Pennes.
Yes, it is possible:
1. Create trigger to set "password" field (object script)
2. Create trigger to send email with "password" field
3. Create Workflow action to run two triggers above
I just tested in my test environment - works fine.
Pavel,
Thank you very much for your explanations and your quick answers on this delicate subject. We were lost.
Matthieu
Marking as resolved