Karen,
Per our discussion a couple days ago… I think you will be better off with the
new (Python, not Java) OAuth interface to MyProxy that is now in the GT repos,
and which is used and automatically configured appropriately for use with
Globus Online by Globus Connect Multiuser.
Regards,
Thanks again Jim,
Correct me if I'm misunderstanding, but in this case I think we're
looking at the latter possibility (#2) if the client id in the
error message
a) matches the client id with (entry key=approvedtrue/entry) in
the clientApprovals/dataPath file and
b) also matches
Jim (everyone),
Sorry to bother.
We added these files to a configuration repository, and I missed changing
the mode for how the file gets re-sync'd.
This whole issue was due to the fact that tomcat was unable to read the
clientApproval xml.
-k
On Fri, Jul 19, 2013 at 07:42:52PM +, Basney,
Karen,
Sorry, I can't explain it. I don't know why oa4mp would log that the
client has not been approved when the corresponding clientApprovals data
file contains entry key=approvedtrue/entry. My only other idea is
to try restarting your oa4mp server, if you haven't tried that already.
Please
Hi Karen,
My only guess is that your oa4mp server is configured to look in a
different store for your clients and clientApprovals than where you wrote
the clientApprovals using oa4mp-approver.jar. What are the contents of the
OA4MP config file pointed to by the oa4mp:server.config.file property
