Hi Douglas,
> In our case we land the user at a login page which handles the httpAuth send
> avoiding
> the nasty dialog.
> If the user is not authenticated they do not get in. No problem there.
> If the user is authenticated then they are taken to the application (written
> in Angular)
> At
Lutz,
Re:
> I'm not really understand your problem. What do you mean with "the browser
> still persists with the username and password"? Does it mean that you > send
> these credentials with every request to the web server?
> What we do is this:
> If the browser makes a request without a
I'm not really understand your problem. What do you mean with "the browser
still persists with the username and password"? Does it mean that you send
these credentials with every request to the web server?
What we do is this:
If the browser makes a request without a cookie or with wrong cookie,
Dani,
Re: Have you looked at the "WEB CLOSE SESSION” command?
That is probably what you are looking for assuming you are using the
built in 4D sessions.
Yes I have looked extensively at that command and I am using it. The examples
all deal with how you would use it with regards the "On
Have you looked at the "WEB CLOSE SESSION” command?
That is probably what you are looking for assuming you are using the built in
4D sessions.
Dani Beaubien
Open Road Development
> On Feb 28, 2019, at 9:38 AM, Douglas Cryer via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> Hello folks,
>
>
5 matches
Mail list logo
