UAA client authorities limit

[tom.s...@opencredo.com]

We're using the oauth2 client credentials flow to control CF-deployed applications' access to other CF-deployed web applications (such as a simple configuration service). Each deployed application has a client defined in UAA with a list of authorities describing its resource access rights. The web application validates the application's access token with UAA and can check it has permission to access a requested resource.

Generally it's working pretty nicely, but we've hit an issue with the size of the client authorities column in the database. Under UAA's postgresql schema the OAUTH_CLIENT_DETAILS.authorities column is currently defined as VARCHAR(256), which is placing quite a low limit on the number of authorities we can grant each application's client.

In the short term we can just extend the size of this column, but that's only postponing the problem. Does anyone have any experience with this? Or suggestions for a longer term solution?

[Filip Hanik]

We'll take care of it

https://www.pivotaltracker.com/story/show/71327966

[tom.s...@opencredo.com]

Great, thanks!

[Filip Hanik]

Tom, 

as we are about to increase this limit, we are also working on an additional feature that may help with this. 

https://gist.github.com/fhanik/bca142df276bab8ca1b1

Great, thanks!

To unsubscribe from this group and stop receiving emails from it, send an email to vcap-dev+u...@cloudfoundry.org.

[Filip Hanik]

Task completed.

https://github.com/cloudfoundry/uaa/commit/6abf14eaf7b482f3cea1e0b3d4fba9f7e9884ffd