B
bart.syryn
Guest
Thanks for the replies. I see that the set-effective-tenant is the easiest way. So in every .p on the appserver side, we would need to set the tenant, and that can be easily done. But maybe it's better to do it the right way and work with CP. We have our own table of users, so we don't use _user. At this moment, when the appserver .p is called, some parameters go along (one is the userid). But I don't understand working with the CP. Correct me if I'm wrong. So the user logs in and the first call to the appserver is made. In our login.p (on the appserver), we check if it's a know user and also check password. If I understand it correct, at that point we should make the CP and store it in a DB or something else together with the session:context-id. When the user is logged in, than we need to pass on every call to the appserver (.p) the session:context-id. Lookup the ID and with the associated CP do SET-DB-CLIENT(CP). I could also use the 'activate' possibility in the openedge management, so that's the .p that is run on every call to the appserver before the .p that actually gets the data, but how do I pass the session:context-id to that .p ? Another question, if you use CP, than you need to set SET-DB-CLIENT in every call to the appserver (stateless), what's the difference at that point with SET-EFFECTIVE-TENANT ? Kind regards, Bart Syryn
Continue reading...
Continue reading...