M
mopfer
Guest
Thanks for the information Bill. The non-Rollbase application is written in the ABL, which doesn’t have much support for making REST calls at this point. I don’t see the Basic-Authentication approach when I’m looking at the SOAP API part of Chapter 15. Am I looking in the wrong place, or is Basic-Authentication only available in the REST API? From: Bill Wood [mailto:bounce-wood@community.progress.com] Sent: Wednesday, May 21, 2014 3:45 PM To: TU.Rollbase@community.progress.com Subject: 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...