Opened 4 months ago

Closed 8 days ago

#1401 closed request (pending)

Authentication failure with Meetecho

Reported by: ekr@… Owned by: Sean Croghan
Priority: tbd Milestone: ietf-108
Component: incoming Keywords:
Cc: My Current Location:
My MAC Address: My OS:

Description

I am now getting a login failure with Meetecho and Datatracker. It worked
fine yesterday. Login is ekr@rtfm.com

Change history (15)

comment:1 in reply to:  1 ; Changed 4 months ago by ekr@…

And now it works. I do not have a captured error trace but it said
something like "checks.state argument is missing"

On Wed, Jul 29, 2020 at 4:02 AM Eric Rescorla <ekr@rtfm.com> wrote:

> I am now getting a login failure with Meetecho and Datatracker. It worked
> fine yesterday. Login is ekr@rtfm.com
>

comment:2 in reply to:  2 ; Changed 4 months ago by ekr@…

And now it works. I didn't capture the error but it says something like
"checks.state argument is missing"

On Wed, Jul 29, 2020 at 4:03 AM IETF Tickets/NOC <tickets@meeting.ietf.org>
wrote:

> #1401: Authentication failure with Meetecho
> ---------------------------+-----------------------------------
>       Reporter:  ekr@…     |                Owner:  < default >
>           Type:  request   |               Status:  new
>       Priority:  tbd       |            Milestone:  ietf-108
>      Component:  incoming  |  My Current Location:
> My MAC  Address:           |                My OS:
> ---------------------------+-----------------------------------
>  {{{
>  I am now getting a login failure with Meetecho and Datatracker. It worked
>  fine yesterday. Login is ekr@rtfm.com
>  }}}
>
> --
> Ticket URL: <https://tickets.meeting.ietf.org/ticket/1401>
> IETF Tickets/NOC <https://tickets.meeting.ietf.org>
> IETF Meeting Tickets - NOC pages
>

comment:3 Changed 4 months ago by Sean Croghan

Resolution: not broken
Status: newclosed

comment:4 Changed 4 months ago by Rick Alfvin

Resolution: not broken
Status: closedreopened

comment:5 Changed 4 months ago by Rick Alfvin

Resolution: fixed
Status: reopenedclosed

comment:6 in reply to:  6 ; Changed 4 months ago by ekr@…

Resolution: fixed
Status: closedreopened
Why did you close this with "not broken"? Intermittent failures aren't "not
broken", they're latent defects waiting to affect someone else.

On Wed, Jul 29, 2020 at 4:18 AM IETF Tickets/NOC <tickets@meeting.ietf.org>
wrote:

> #1401: Authentication failure with Meetecho
> ---------------------------+-----------------------------------
>       Reporter:  ekr@…     |                Owner:  < default >
>           Type:  request   |               Status:  closed
>       Priority:  tbd       |            Milestone:  ietf-108
>      Component:  incoming  |           Resolution:  not broken
>       Keywords:            |  My Current Location:
> My MAC  Address:           |                My OS:
> ---------------------------+-----------------------------------
> Changes (by Sean Croghan):
>
>  * status:  new => closed
>  * resolution:   => not broken
>
>
> --
> Ticket URL: <https://tickets.meeting.ietf.org/ticket/1401#comment:3>
> IETF Tickets/NOC <https://tickets.meeting.ietf.org>
> IETF Meeting Tickets - NOC pages
>

comment:7 Changed 4 months ago by Rick Alfvin

Owner: changed from < default > to Sean Croghan
Status: reopenedassigned

comment:8 Changed 4 months ago by Sean Croghan

Eric,

Apologies for the not broken close. The quick update from you that you were connected resolved issue that this ticket system is for.

After reopening the ticket I had the tools team check for any errors and none were found.

Further inquires discovered that this error can occur when there's no cookie associated to the session.

Do you have cookies disabled or had them cleared? What were the steps that you did after the error that allowed you to connect?

comment:9 in reply to:  9 ; Changed 4 months ago by ekr@…

>
>  Further inquires discovered that this error can occur when there's no
>  cookie associated to the session.
>
>  Do you have cookies disabled or had them cleared?


No.

What were the steps that
>  you did after the error that allowed you to connect?
>

I reloaded the page and tried again.

comment:10 in reply to:  10 ; Changed 4 months ago by ekr@…

This just recurred

On Wed, Jul 29, 2020 at 5:03 AM IETF Tickets/NOC <tickets@meeting.ietf.org>
wrote:

> #1401: Authentication failure with Meetecho
> ---------------------------+------------------------------------
>       Reporter:  ekr@…     |                Owner:  Sean Croghan
>           Type:  request   |               Status:  assigned
>       Priority:  tbd       |            Milestone:  ietf-108
>      Component:  incoming  |           Resolution:
>       Keywords:            |  My Current Location:
> My MAC  Address:           |                My OS:
> ---------------------------+------------------------------------
>
> Comment (by ekr@…):
>
>  {{{
>  >
>  >  Further inquires discovered that this error can occur when there's no
>  >  cookie associated to the session.
>  >
>  >  Do you have cookies disabled or had them cleared?
>
>
>  No.
>
>  What were the steps that
>  >  you did after the error that allowed you to connect?
>  >
>
>  I reloaded the page and tried again.
>  }}}
>
> --
> Ticket URL: <https://tickets.meeting.ietf.org/ticket/1401#comment:9>
> IETF Tickets/NOC <https://tickets.meeting.ietf.org>
> IETF Meeting Tickets - NOC pages
>

comment:11 Changed 4 months ago by Sean Croghan

Details?

I'm guessing your experience was...

You exited the first session for the break. Was that by clicking the leave room button or closing the browser window?
When you attempted to open the second session you received the error?
You then Reload/refresh the page and that resolved and you were able to connect?

comment:12 in reply to:  12 ; Changed 4 months ago by ekr@…

>
>  Details?
>
>  I'm guessing your experience was...
>
>  You exited the first session for the break. Was that by clicking the leave
>  room button or closing the browser window?
>

One than the next.


 When you attempted to open the second session you received the error?
>

Well, it reported "Success" but didn't actually log me in and then when I
clicked log in again, it failed.


  You then Reload/refresh the page and that resolved and you were able to
>  connect?
>

No. I then went to another WG (dnsop) and *that* worked. And then when I
came back to the original WG (tsvarea) it worked.

comment:13 Changed 4 months ago by alex@…

Eric,

may it be that you opened the login page *of the same session* in two browser tabs? In this case the session cookie could be consumed by the second page, hence resulting in an invalid state in the former due to a missing cookie. This has been fixed now, please let me know if you still experience this.

comment:14 in reply to:  14 ; Changed 4 months ago by ekr@…

On Wed, Jul 29, 2020 at 2:57 PM IETF Tickets/NOC <tickets@meeting.ietf.org>
wrote:

> #1401: Authentication failure with Meetecho
> ---------------------------+------------------------------------
>       Reporter:  ekr@…     |                Owner:  Sean Croghan
>           Type:  request   |               Status:  assigned
>       Priority:  tbd       |            Milestone:  ietf-108
>      Component:  incoming  |           Resolution:
>       Keywords:            |  My Current Location:
> My MAC  Address:           |                My OS:
> ---------------------------+------------------------------------
>
> Comment (by alex@…):
>
>  Eric,
>
>  may it be that you opened the login page *of the same session* in two
>  browser tabs?


No, that's not what happened.


In this case the session cookie could be consumed by the
>  second page, hence resulting in an invalid state in the former due to a
>  missing cookie. This has been fixed now, please let me know if you still
>  experience this.
>

Willdo.

comment:15 Changed 8 days ago by Sean Croghan

Resolution: pending
Status: assignedclosed
Note: See TracTickets for help on using tickets.