K
kevin hermans
Guest
If I understand you correctly you make a call to a PAS AppServer and the userid doesn't get set on the database(setuserid) when doing a REST call after authenticating. When doing the authentication you don't have a dedicated agent where your userid is set. Every time there is done a REST call, your user get an exclusive moment with your agent for getting the job done and then will return the needed info. Afterwards another clients gets connected and so on... From the moment your user connects to the agent the activate procedure from the PAS will get triggered and there you have to set the userid just like with the Classic AppServer. A print screen where you can set the activate procedure. You can set a message in your connect procedure and check the logging I hope this helps: define variable vhCP as handle no-undo. assign vhCP = session:current-request-info:GetClientPrincipal(). message "after GetClientPrincipal() : hCP= " vhCP skip " session-id= " vhCP:session-id skip " login-state= " vhCP:login-state skip " USER-ID= " vhCP:user-id skip " QUALIFIED-USER-ID= " vhCP:qualified-user-id skip "DOMAIN-NAME" vhCP:domain-name skip view-as alert-box.
Continue reading...
Continue reading...