M
Mike Fechner
Guest
Hi Bill, do you know how that‘s going to be different in the URL’s for REST calls? Just add the auth-header and skip the session ID in the URL? We’ve implemented our own ABL REST Adapter to Rollbase (based on sockets) and using Basic-Auth instead of the extra login call sounds promising! Mike Von: Bill Wood [mailto:bounce-wood@community.progress.com] Gesendet: Mittwoch, 21. Mai 2014 22:45 An: TU.Rollbase@community.progress.com Betreff: Re: Is it possible to have two valid Rollbase sessions for the same userID at the same time? Re: Is it possible to have two valid Rollbase sessions for the same userID at the same time? Reply by Bill Wood As you noted, sessionID is limited to one active session per user credential, but you can also authenticate individual requests with Basic Authentication. (See Chapter 15 in Rollbase In Action). The sessionID is useful when you want to hold the authentication across multiple requests. Using Basic-Authentication means each request contains the username/password so you should only do this over https, but because requests are self-contained you won't run into conflicting sessions. I believe this was added as a grater in Rollbase 2.2. = Stop receiving emails on this subject. Flag this post as spam/abuse.
Continue reading...
Continue reading...