I recently started working with KeystoneJS, walked away for a week, and now I can't log back into my admin dashboard.
Behaviour:
Enter a valid username and password, observe a 200 success response, and no error message in the console or on-screen. Unable to access any other path than:
http://localhost:3000/admin/signin
Enter a bad credential and get notice that the username or password are incorrect (indicates that the service is working)
It seems like the credentials are accepted based on the payload (which returns my password in plaintext and that feels weird). Is this a well-known issue tripping up a newbie? Or something different?
For me, this was an npm command line issue. Instead of using npm start I found npm run dev to work. For my development purpose, that resolves this issue. May come up on live, as I've seen it reported in the KeystoneJS Slack as well.
Related
Until a few days ago I was deploying my html on Github pages with:
ng deploy --base-href=/documentation/
Today I get this error: "remote: Support for password authentication was removed on August 13, 2021. Please use a personal access token instead.
remote: Please see https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/ for more information.
fatal: unable to access 'https://github.com/BioComputingUP/ProSeqViewer-documentation.git/': The requested URL returned error: 403"
I have set a token on my github settings, but I don't understand how to use it to deploy my pages. How should this be done?
I discovered 2 ways:
use the token when the IDE prompt asks for the password. I have tested this end it works.
set keys. (I have not tested this).
when I try to login to my Heroku account, after I enter my 2FA code, I get the green 'checkmark' as usual, but afterwards I am greeted with a Salesforce error screen, saying 'Problem Approving Your Request'.
Error Message Salesforce
I have tried multiple times over the span of an hour, but I still get the same error...
Is it an issue on my side? or is something broken at Heroku?
Thanks
I got this exact problem when using Waterfox. I switched to Chrome and was able to log in. If you're using a non-tracking kind of browser that might be the problem.
I just installed the Keystone yeoman generator and ran the yo keystone command. I went through and entered the email, password, and all the other fields in the set up.
I can run the Keystone App just fine, but when I go to sign in to the admin UI it won't accept my credentials. On the welcome page it tells me that email and password to sign in with so I know I'm using the correct credentials. I checked the User.js model and everything looked fine. I'm new to Keystone and have no idea what the problem could be. I looked through the Keystone docs and for answers elsewhere but have found nothing.
I confirmed this to be a bug in Keystone. I submitted a pull request (#1326) to address this issue just a few minutes ago.
I will update my answer as soon as it's merged. It was just merged! :-)
Apparently Keystone converts any capital letters in an email address to lowercase. If anyone else runs into this issue and has a captial letter anywhere in their email for login, use all lowercase letters and it will then work!
For some strange reason, I can no longer access tumblr's API console:
https://api.tumblr.com/console//calls/user/info
It takes me to the authorize page, but once I click "allow" I just get redirected back to the login page. Strangely nothing has changed, my python script still has access. I tried creating a new account, new app, on a new IP. But I still can't get into that stupid console!
I got an email from the developers at tumblr, it looks like they fixed the problem:
My apologies for the extremely late response. We had an issue with this page which has since been fixed.
Hope it didn't cause you too much trouble!
We have done a fair amount of work and have come pretty close to getting Jenkins to automatically kick off a build when a push is made into Github. However, Github is logging an error from Jenkins when attempting to post to the Github plugin webhook as follows:
Error 401 Either no such user 'CN=Github Account,OU=Jenkins,OU=Applications,DC=mydomain,DC=com' or incorrect password; nested exception is javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 52e, vece?]
We have LDAP enabled in our environment to allow for active directory logins. An account called "github" has been created on our domain and authorized as a Jenkins user. We are able to manually login to Jenkins by punching in the username and password for this account and it works as expected. The "github" account has been authorized on the project for READ and BUILD directives on the job.
On Github, the push webhook has the url defined as follows:
http://github:password#jenkins.mydomain.com:8080/github-webhook/
We can confirm that the push event effectively triggers the post to the URL, but the response is a 401 with error details as described above. We know the account is valid and the password is correct, but we are stuck because we cannot understand why Jenkins suggests that it is invalid.
We have used the following link, among many others as a guide:
http://fourkitchens.com/blog/2011/09/20/trigger-jenkins-builds-pushing-github
As far as we can tell, the only difference between our configuration and those of others who have posted about their success on blogs and here on Stackoverflow is our use of LDAP authentication.
Does anyone have any guidance to help us overcome this hurdle? Currently, we can successfully run a build manually, so our communication TO Github FROM Jenkins is tip top. But Github back to Jenkins is a frustrating no-go.
This is now working. Here is what went wrong. When configuring the following string, pay careful attention to both the username and password:
http://github:password#jenkins.mydomain.com:8080/github-webhook/
In our case, the password contained special characters that Jenkins was tripping over. Usernames and passwords with special characters must be URL encoded or the authentication will fail. For example, the following password
!test+pw
must be URL encoded as follows:
%21test%2Bpw