You are not logged in.
When creating new users, or updating passwords, they cannot login if there are email issues that occur during the saving process.
This seems very weird as the changes seem to be saved in ReportServer but clearly some, or all, of it is not.
We've had some problems with email configuration during testing due to issues outside of our control, but this has led to many hours of wasted time trying to understand why our test users can't login when we keep updating the password and checking access permissions.
Surely it would be better to save the users details and perform an offline email send, rather than delay the save until an email operation completes. This does not logically make any sense to me. These should be separate actions that are carried as part of creating or editing a user, not one whole transactional process. For example updating a password looks like it works, then 1 minutes later after some email related issue you get a popup message, probably while you are on another form. It makes no sense that that the user details have not yet been updated.
This is deeply frustrating when setting up a test system where you absolutely no interest in sending emails. Why do you need to configure a mail server just so you can add a few test users. It makes no sense at all. All it does is waste time for new users because it looks like you've done everything correct in setting them up but none of them can log in.
Last edited by ianef (2024-07-31 14:53:14)
Offline
Hi Ianef,
again we apologize for your wasted time!
you can leave the "email" field empty for every user. One you "apply" (save) the user, he is available to login. BUT clicking the "activate"-Button will trigger the reportserver to send an email to the given emailadress... if this is empty or no email is configured => an error will occure
sure, this is a bit counter-intuitive... I've stumbled upon this behaviour myself many times.
kind regards
Felix
Softwareentwickler bei Infofabrik
Offline
Thanks Felix. I think there is some work to be done. There are some improvements that I would like to see in place here:
1. Remove or completely comment out the contents of mail.cf.
2. Pre-configure a disabled email datatsink, just so users can see where the settings are. It must be set to disabled, this is really important.
3. When updating a user, if the Activate button is clicked and no active email server is configured, show a warning popup indicating that no activation emails can be sent. Do nothing else.
4. When applying changes to a user, if the user has an email address but no active email server is configured, show a popup message indicating that no user update messages can be sent.
Offline
Hi ianef,
thanks for your improvement suggestions. I raised RS-8575 for looking into this. We will consider them in future versions.
Regards,
Eduardo
Offline