Return to Project-GC

Welcome to Project-GC Q&A. Ask questions and get answers from other Project-GC users.

If you get a good answer, click the checkbox on the left to select it as the best answer.

Upvote answers or questions that have helped you.

If you don't get clear answers, edit your question to make it clearer.

+1 vote
320 views
It would seem that the Geocaching.com authentication routine has to be re-rerun every time I switch from one device (or one browser) to another. If I stay in the same browser it stays authenticated for however long, but the instant I use my mobile, another PC or even another browser (IE11 from Chrome for example) PGC has to re-authenticate. Then the instant I switch back to the previous browser it go again.

I believe the token can cope with multiple links as other geocaching.com authenticators cope fine. It is just Project-GC that has to get a new one. Can this be remedied please?
in Bug reports by Pprime (P`) (230 points)

1 Answer

+1 vote

Think project-gc is still handling the issues with the new geocaching.com API.

As there are these authenticators issues also on the GC.com site (as you mentioned), project-gc perhaps wait until gc.com has fixed there issues.

Have the same problem using project-gc and also have the same issues with firefox, chrome on my deviced getting into gc.com

We all like single sugn on and authenticators only once - but we all like security (with our username, pw and account). Think they are just try to get this as useful as possible.

==> think we have to wait

by supertwinfan (19.6k points)
...