Skip to main content
  • EN

I put Box Sign projects on hold for a year in hopes box.com would fix various web UI bugs in

signing documents.

Sadly, I still see an unacceptable overstrike and now even multiple font sizes on that overstrike, etc.

 

But now that I’ve come back, I find that I can no longer get CCG to work with the User ID set in

the app.  ( CCGAuth() in Python SDK. )  The initial authorization works when using Enterprise ID

BUT that is not what I want because when using the Enterprise ID, it never could access my

templates--They were only accessible when using the user id.  (the User ID in the app config.)

( It was previously able to access them when using the “user” argument to CCGAuth(). )

I changed nothing.  It stopped working.  Yes it was still authorized then reauthorized for good measure.

Is this a bug or a feature?  And is there a way to get the old behavior?  Other than this:

Sadly I had to switch back to regular OAuth2 using the annoying 1 hour temporary dev tokens

where it still will access the template files owned by the app’s “User ID” user.

 

 

I’ll reply to myself.  The mentioned breakage appears to be from an API security change.

My app’s previous App Access Level was Only App Users of This App.  I changed it to

App + Enterprise Access and it started working again.

Not sure if the previous way I got a Client Credentials Grant for the App’s owner User was a bug

or a feature, but the way it now works seems reasonable.  Was there a memo that I missed?

Note that the change in App Access Level was needed despite still having these checked:

Read all files and folders stored in Box
Write all files and folders stored in Box

 

I saw another post that mentioned access going away without any app changes, so if this happened

to you, try changing the App Access Level.  HTH

 

Hi there, ​@Moo 👋 Welcome to Box Community! Thank you for sharing your insights regarding the CCG issue. We’ll definitely review the error you encountered in the past, though I’m glad you have resolved this by changing the App Access Level.


You can always refer to our Developer Guides and API reference in case you run into issues related to API in the future.


Thanks for your great contribution! 💙

Reply


Terms & ConditionsCookie settings