Something went wrong with adding the app authorization
Answered
Hello, May I ask you a question about “Authorize New App”. In details, I navigate to Enterprise “Admin Console > Besenise Settings > Apps” (https://app.box.com/master/settings/openbox ), click on “Authorize New App” button. In the pop-up window, I entered “API Key” for the Application to be authorized; then click “Authorize”button in the following pop-up window. But, I got the error message “Something went wrong with adding the app authorization”. The application is created with Authentication Method as “App Token (Server Authentication)”.
BTW, I have successfully Authorized New Apps of Authentication Method as “OAuth 2.0 with JWT” before.
Thanks!
-
Hello Elaine,
also not really the perfect wording, the error message is though 100% correct and it works as designed. App authorisation is only necessary and makes sense for JWT access.
The JWT access is meant for server side applications, that you do not want to be prompted for passwords and ask them for granting access every time. Thus you also need a private / public key pair for them, and here authorisation makes sense.
For OAuth2 you are redirected to a login page and then asked to authorise, so no need for doing this via the admin console, as you do not want any user have access to your data.
For AppToken the scope is fixed, always the same and who ever owns the token has a certain subset of rights, so there is no need for Admin Console authorisation either.
So what you experienced is totally correct. JWT works, the other two don't.
I hope this answers your question.
-
Hi ,
I am having the exact same behavior that Elaine has described above, and just like her I am getting an error both when I try to create an App Token or when I try to grant the app authorization. So one of those errors can't be expected, and I tend to think you might be miss-informed about not needing to authorize apps that use App tokens. I think this because of what is said on this (https://developer.box.com/v2.0/docs/getting-started-with-new-box-view) page about setting up an App that uses app tokens:
"This app has to be authorized by the enterprise administrator" error
If you receive this error when trying to generate the App Tokens, please request your Box Enterprise Admin to follow the instructions here (see the section "Grant Access in Enterprise Admin Console") to authorize your application in the Admin Console. Admin must use your New Box View application's API key when prompted to enter the client id in the authorization flow.
Once authorized, you should be able to generate the Primary and Secondary App Tokens.
That blurb is taken directly off of the developer page and clearly indicates that the app still needs to be authorized. Please respond with more information/context than as there is LITERALLY NO documentation on this issue except this post and the blurb I posted above.
Thanks,
- Feste
-
Hi Feste,
for older (i.e. longer existing accounts) box support has to activate a feature to make the AppToken work. Please open a ticket with Box Support to have the AppToken activated, Also note that after activation create a new AppToken, as the activation is not working on prior created applications.
The documentation is unfortunately not accurate, an AppToken does not need Admin authorisation.
-
Hi .
I have a new application with App Token (Server Authentication) as the Authentication Method. When I try to generate the primary access token, I get the "This application needs to be authorised by the enterprise admin" error.
When I try to authorize it on Admin Console, following the instructions that said, I have the "Something went wrong with adding the app autorization".
My account is new, so I shouldn't ask to box support activate my AppToken, right?
What can I do to generate the key?
Thanks!
-
Hey all, I just wanted to update this post with the solution that I found. It may have changed since I got this working, but in my case it turned out that 'admin flag' wasn't something that is actually exposed to an admin on the account. In this case it was more of an engineering admin flag, and to get it set I had to contact Box support directly and ask them to file a ticket so an engineer could enable that flag on the account. To re-iterate this is not something an end-user can do on his own, but rather something that is done on a per account basis by engineers at Box.
Maybe that will change over time if this is a highly requested feature, but who knows. I hope this helps.
-
Hi ,
Welcome to the Box Community and thanks for your first post in the forum!
Kindly visit this article for the Steps to Resolved the issue:
Please Note that Co-admins do not have the permission to manage other co-admin accounts.
Be sure to read our guidelines, Subscribe to content you like, and complete your profile on the community.
Please sign in to leave a comment.
Comments
11 comments