I have a customer community and I'm encountering an issue where after a customer community user takes some actions in my community they are automatically logged out. I believe that this is because the session ends with the action they are taking. Is there a way to keep them logged in? I've already gone to the Session Settings and unchecked "Force logout on session timeout" but it isn't changing anything and my user is still being logged out.
Related
I'm having this problem with my application where it will eventually (unsure of the timeframe, presumably 1 hour) stop updating live with firebase realtime database changes without logging out and back in. The security rules prevent unauthorized users from accessing data. The user will remain logged in and the authentication session persists, so I've been miserably confused as to why it eventually stops updating.
After a painful amount of internet scouring, I've come to find out that the token ID given on login lasts only 1 hour, at which point they are refreshed automatically using the refresh token. (For the record I am logging in with firebase.auth().signInWithEmailAndPassword).
Now, my question - Do I need to resubscribe to my database after the token ID is refreshed? More specifically, do I need to call firebase.database().ref().off() and then subsequently call firebase.database().ref().on() when a token refresh is detected? If not, can you possibly point me in the direction of what might be going wrong?
Edit: It may also be worth noting that if I change my security rules to allow unauthenticated reads, the user is still able to write to the database indefinitely without having to reauthenticate.
Firebase passes the new authentication token to the database automatically. As long as the user remains the same, you don't need to reattach the listeners.
The only moment you might have to reattach is if the user somehow becomes signed out. This may happen when the ID token can't be refreshed, for example because the account has been disabled, or the password has been changed. In that case the existing listeners will be canceled, which will be logged in the client, and the (optional) error callback for on will be invoked. At that point you'll need to reauthenticate and attach new listeners.
We have a lightning community, as well as a VF community that holds a cloudcraze/B2B commerce storefront. Within the lightning community we are calling cloudcraze APIs for things like user registration.
Currently, we are successfully registering users (by calling the cloudcraze user registration API). Immediately after registering a user successfully, we call the Site.login() method to log the user into the community. Both registration and login are successful - we have confirmed this through debug logs and by checking the login history of the org to see that those users have logged into the proper community.
Unfortunately, we are facing a weird problem where the current user doesn't seem to change. Using debug logs, we see that the current user is the same both before registration + login and after (it's the community guest user).
If we log in through Salesforce by going to a contact and clicking "Log into community as user", Salesforce correctly recognizes the current user.
I am developing an internal application with multiple users and one administrator.
i am allowing only 50 users can login into the application at a time, after that i won't allow any other user to logged in.
Now, from admin side i want to kill the specific user session and authentication from logged in users, before killing the user session and authentication i want to prompt a confirm dialog with ok and cancel , depends on the response i want to kill the user.
My question is how to prompt the confirm dialog in the other logged in user screen and how to capture the response.
i am using spring security and angualarjs.
can anyone provide a solution. Thanks in advance.
I have a serious login problem with my new (and first ever) Drupal 7 site.
I have two different users so far, which of one is the admin which was created while installing Drupal. If, I log in with the other user's username and password, still, the hovering admin menu will and the menu shows the username of the admin user. This happens, if I log in to both accounts from the same computer, but now I tested the non-admin account from a computer that have never been used to log in the particular site before, and the problem
I am using the current 7.34 core of Drupal 7. The login module is the built-in one of the core.
How is this possible and what can be done about it?
Remove cookies from your browser for this site
Make sure your second user has not admin role.
I recently, refreshed my sandbox. and logged out. The next time I tried to log in, it did not let me log in. Also, there was an email notification for new security token (which was neither requested nor the password was changed). How can this be? And how can I start logging in again.
Thanks
Refreshing your sandbox will effectively create a new Salesforce org with a new unique OrgId.
Part of this process modifies all the user names that were copied form production to be unique as well. As these are all new users they get new security tokens to be distinct from the production users. The password immediately after refresh will be the same as production.
See Knowledge Article: Sandbox login and password