OAM SDK Error

Question

Hi,
I have an Access Gate installed on my Windows Desktop and wrote a test program with the SDK. I'm able to obtain policy information by using the getPolicyDomains() method and it returns the correct number of policies, etc.
What I really need to do is run a "test" because I want to find out if a certain user will be able to access a certain resource. It doesn't work. I sent my code to someone else and it works for them--using their own OAM installation. So I'm thinking there is something wrong with the way OAM is installed on our boxes.
As I said I can get the policy information, but the testAccess method bombs. Eclipse displays OAM debug information, however I don't get any message from the exception that catches the error--it's just null. i'm testing with user OblixAnonymous to see if he can access abweb4o.
Does this debug output indicate what the problem could be? It's messy. Thank you in advance.
1-6-2011 14:41:19Sending message: 2 17
am=v%3d%201;req%3d+10;admtok%3d+108:39rI0HCmLkTHimbYzCH/tgnhSK9quO/XBiE8LYc4VwmzJaezfCqTYEeckcShklIpVBR0mSv2hghWTXAhu1QD1nfT+M9U++6uE2E9llRTrQc%3d;test%3d%20url%3d%2018:abweb4o/index.html;restype%3d%204:http;op%3d+3:GET;op%3d+4:POST;user%3d+uid%3d%2014:OblixAnonymous;login%3d%2014:OblixAnonymous;;showallowed%3d%20T;showdenied%3d%20T;; sc=true
1-6-2011 14:41:19Received message: 2 17
st=ma%3d57%20mi%3d2%20sg%3d0%20sm%3d am=v%3d+0;except%3dcode%3d+219;p1%3d+251:\Oblix\10143hf\palantir\dblib\src\user_db.cpp:687:%20Error:%20Exception%20re-thrown%20in%20UserDB::CheckUid.%0a\Oblix\10143hf\palantir\dblib\src\user_db.cpp:683:%20Error:%20Unable%20to%20search%20the%20Directory%20Server%20because%20of%20Operation%20not%20supported.%20in%20UserDB::CheckUid.;p2%3d+0:;;
failed with Message=null <--this is the exception message content

Answer 1

Hi Sazama,
Oracle does not usually share its source code, at least without a contract in place.
As you say, if the Policy Manager is happily returning authorisation results for the OblixAnonymous user (and you tested when logged into the Policy Manager as the same user who logs into the AccessGate app) then that does show that ldap is OK, and that Policy Manager is configured correctly to use it. However, with the ASDK application it is the Access Server that will do the search (Policy Manager communicates directly with ldap) so it is worth going into the Identity System Console and checking that the Directory Profile the Access Server is using is setup correctly (compare it with the one the Policy Manager uses, for example). I can't really unserstand what the problem is, or why it would have happened, but I believe that the problem is in that area (though I will keep an open mind, of course :-) ).
I assume that the Access Management Service is also on for the Access Server that the AccessGate connects to?
Regards,
Colin