When I am trying to log in to my Heroku account it tells me to use the authenticator app.
I downloaded the salesforce authenticator, but I think I have to be inside my account to make the connection to the app. But I can`t get in to do that - Its a typical catch 22 situation.
Related
Please Help!
I am unable to login into my heroku account even I know my correct login id and password due to the 2FA which was enabled mistakenly with me because I needed to deploy my app quickly.
I used Google Authenticator for generating the authentication code and logged in but next day my mobile got damaged in a way which couldn't be repaired. Due to which when again I tried to login it still asks for google generated verification code which I don't have, I contacted heroku support several times but it's been a month but still I couldn't get any satisfactory response.
They have opened some Temporary code login and provided a recovery code but still I am unable to login.
Anyone Please help me get my account
Page where I am stuck
My local Django app has an admin account, which I can successfully login to. However, when I deploy this app to the Google's Cloud by following this tutorial; I get the photographed error. How can I fix this?
I'm currently developing a Flask application on a Amazon EC2 instance running Linux. I have installed httpd and access to the site is successful. The Flask application has an OAuth2 authentication using Google accounts.
When testing on localhost, the website runs perfectly with the user staying logged in. However, when testing on the live site - there is a redirect to the Google login page after about a minute. Apart from this, the live site is working as expected including the actual process of logging in.
Does anyone have any ideas why this is the case or have suggestions on how to fix this? I can provide more details on the setup if need be. It seems strange that the localhost doesn't have this issue.
Make sure you're using UTC everywhere.
Check:
https://www.googleapis.com/oauth2/v1/tokeninfo?access_token=[access_token]
to see the expiration time of your access token.
I'm trying to develop a rally app using the app builder. When I load App-debug.html in my browser, I am prompted to enter my user credentials in the form provided. I enter them, but the form re-appears over and over again.
I did notice that the login attempts to authenticate via https://rally1.rallydev.com:443. If I go to this in another window and enter my account details I am able to get in. However, when I do log in, there is a corporate redirect that takes place (for SSO) and I ultimately end up on us1.rallydev.com.
How would I get my app to authenticate through us1.rallydev.com. Changing urls in App.js and config.json only causes errors when trying to load javascript for APIs.
The app should always just piggyback on your existing session. Changing the serverin config.json and re-running rab build should cause all traffic to go to that server- if that's not happening then that's a bug.
You won't be able to authenticate from scratch using SSO from an app, but it should have no problem re-using an existing session.
Another option is to use an API Key to develop: https://help.rallydev.com/apps/2.0/doc/#!/guide/embedding_apps
I want to know what are the best practices, when using Worklight:
To Logout
To Maintain the user logged in, after application relaunch.
To login a user directly after an account creation
I am using Worklight 6 authentication, with a custom login module, for an Hybrid App (HTML5)
If there is a sample doing all these feature, it will be great, otherwise, any code snippets and advices should help me.
Thanks
Can't exactly say that these are 'best practices', but this is what I would do in these situations:
To Logout
Don't have much to say here. Clear anything and everything that the user could use to access resources on the server, including cookies. As you probably know, the login modules come with a logout function call where you can perform these operations.
To Maintain the user logged in, after application relaunch
After the first login, use some local storage mechanism, such as JSONStore, in order to save the credentials. JSONStore can encrypt all data saved locally as well. When the user starts the app, instead of prompting for login credentials, check the local storage to see if the credentials already exist and then send them to the server to log in.
To login a user directly after an account creation
I'd use a similar approach as above. When the user sends their account information to the server, save it to local storage. If the account creation was successful, then the server can send a success response to the client which can then automatically send the credentials back to the server to log them in. If the server sends a failure response, then the credentials should be deleted from the local store and the user will be prompted to try to register again.