You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
When creating a repository using the bitbucket API I am suddenly getting the following error, despite everything working previously:
Error: API Error: 403...Too many invalid password attempts. Log in at https://id.atlassian.com/ to restore access.
I have tried all the usual, and the suggested elsewhere, methods of overcoming this issue:
Is it possible the API error is actually incorrect? One possible explanation is that I may have hit the API too many times in a set period using the app password?
Does anyone have any suggestions?
Grant
To answer my own question here (yes, I am build_services):
Turns out that I had the app password in two places, and never updated it in one of them 🤦. But the API error is incorrect as logging in at https://id.atlassian.com/ does nothing to help the situation in this case; and the error is brought about not by a frequency of invalid log-in attempts in this cause, but only 1.
The API error should perhaps simply read: 'Incorrect password attempt'.
Maybe youd let us know where these "2 places" actually exist so as to help others???
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry both, you're right, I should have added more detail at the time bc now I'm not 100% sure what those 2 places are. IIRC I had updated my password in `postman` but not in my kubernetes job that was doing the work that postman was simulating, so probably not the answer you are looking for anyway
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.