Without seeing how this is configured, without seeing any pertinent stack trace, and without being terribly familiar with the Gradle Spring Social plugin (I assume you're using that), I can only speculate...but...
In a typical Spring Social configuration, the API bindings are provided with their access tokens via the user's primary connection...and the user's primary connection is retrieved using the currently authenticated user. If you're not logged into the app, then there is no current user and thus no way to lookup the user's primary connection. The only Twitter API binding you'd get is the default one that would only allow you to do operations that don't require authorization. The "Authorization revoked" exception seems a bit surprising...I'd expect that you'd get a MissingAuthorizationException. Is that perhaps what you're getting?
Spring Social Project Lead