P
Peter Judge
Guest
But if you would use the session-id on the client side to pass that to the appserver. How can the activate.p on the appserver recieve that parameter ? I don't see how we could pass it and check it. In the activate.p, you can get SESSION:CURRENT-REQUEST-INFO:ClientContextId . In https://github.com/nwahmaet/IdM_Sample/blob/master/idm-appserver-bl/services/BusinessLogic/Activate.p ,from the sample I mentioned earlier, I do: run Security/GetClientPrincipal.p on hSecurityTokenService ( session:current-request-info:ClientContextId, output cToken). rClientPrincipal = base64-decode(cToken). create client-principal hClientPrincipal. hClientPrincipal:import-principal(rClientPrincipal). /* now user is set to requesting user */ security-policy:set-client(hClientPrincipal). GetClientPrincipal.p above simply retrieves a raw-encoded version of the C-P from a database table, and returns it to the caller in base64 encoding. So everytime there's a request on the appserver the activate.p would run, and checks the session-id and CP to set the client. Has that a great influence on performance ? I would think there's some impact, because there's some work being done. However, there are also costs incurred by not doing this work. -- peter From: bart.syryn [mailto:bounce-bartsyryn@community.progress.com] Sent: Friday, 21 February, 2014 09:56 To: TU.OE.Development@community.progress.com Subject: RE: Multi-tentant - appserver - webspeed RE: Multi-tentant - appserver - webspeed Reply by bart.syryn We're planning to use 11.3.2 to set this up. So I suppose that Client-context-id is available. But if you would use the session-id on the client side to pass that to the appserver. How can the activate.p on the appserver recieve that parameter ? I don't see how we could pass it and check it. We use stateless, so when the user logs in, we make a connection to the appserver. The connection isn't closed, only when the users logs out of the application. Every time there's a request to the appserver, we check at the client side if the handle-appserver is still valid, if valid just run the .p otherwise make a new connection. So everytime there's a request on the appserver the activate.p would run, and checks the session-id and CP to set the client. Has that a great influence on performance ? Stop receiving emails on this subject. Flag this post as spam/abuse.
Continue reading...
Continue reading...