Why was a login forced today?

https://community.logos.com/discussion/comment/749107#Comment_749107

I too had to sign in today and a number of other uses said they did too. So far we don't know why but it was obviously some sort of system update.

John Kight

Here is an additional thread as well:

https://community.logos.com/forums/t/113006.aspx

Francis

https://community.logos.com/discussion/comment/749113#Comment_749113

I believe that this is to confirm to new regulations with regard to user permissions. You may have noticed that it gave permission to Faithlife to use user information. It seems also consolidated under the Faithlife banner.

Donnie Hale

https://community.logos.com/discussion/comment/749144#Comment_749144

I believe that this is to confirm to new regulations with regard to user permissions. You may have noticed that it gave permission to Faithlife to use user information. It seems also consolidated under the Faithlife banner.

A reasonable explanation... But I would really like a definitive answer from FL. I had to sign in to the Bible app on iPad and on iPhone. Plus, I had to sign in on the forums site *and* on www.logos.com. Neither of those sign-ins surface any kind of agreement.

-Donnie

My Faithlife Bible app forced me to log in this morning. I'm not sure why. I note that the forum site also forced me to log in as well.

Anyone know why this happened? I haven't seen anything in the forums explaining what might have happened.

Thanks,

Donnie

There was a login bug and part of the fix required all tokens to be invalidated. Sorry about the resulting re-login.

https://community.logos.com/discussion/comment/749144#Comment_749144

I believe that this is to confirm to new regulations with regard to user permissions.

This is not the case and there are no "new regulations".

Francis

https://community.logos.com/discussion/comment/749179#Comment_749179

I mentioned this because I have noticed that across the board websites are systematically and more visibly asking for permissions now and I seem to remember there was a permission asked with the sign-on today whereas former sign-on procedure did not include one. I supposed it was not a coincidental happening across the net...

I am not sure about US regulation but cookie regulation has changed in the EU since 2012. See https://en.wikipedia.org/wiki/HTTP_cookie#EU_cookie_directive

https://community.logos.com/discussion/comment/749187#Comment_749187

This was also not the case, no new permissions were added.

ManilaDave

https://community.logos.com/discussion/comment/749177#Comment_749177

I have most of my library downloaded on my iPad - 3,000 plus volumes. They are no longer downloaded as a result of the forced log in. there is now a time and an internet cost factor as a result of your bug

https://community.logos.com/discussion/comment/749250#Comment_749250

I have most of my library downloaded on my iPad - 3,000 plus volumes. They are no longer downloaded as a result of the forced log in. there is now a time and an internet cost factor as a result of your bug

That is unfortunate. Bugs do happen despite our best intentions. As always, I strongly recommend that nobody download thousands of books locally to their device unless absolutely necessary (i.e. they are without any access to the internet for a lengthy amount of time and will need every single one of those thousands of downloaded books during that time).

I personally think we should have removed the "Download All" option long ago because it has the potential of misleading customers into thinking it will improve the mobile experience or speed up the app. To the contrary, it has mostly caused anguish for customers who might have to re-download thousands of resources should something go wrong (like happened last night).

Matt Hamrick

https://community.logos.com/discussion/comment/749256#Comment_749256

I like the Download All for an author's works when I search for author, I don't use it otherwise but if you remove it I can live with that.

Francis

https://community.logos.com/discussion/comment/749212#Comment_749212

This was also not the case, no new permissions were added.

I had never seen this before yesterday (the parts highlighted in yellow in the picture below):

Don Awalt

https://community.logos.com/discussion/comment/749351#Comment_749351

I think I noticed another symptom, on both computers I had the red exclamation point where sync was - I manually tried sync and the '!' would almost immediately come up. I exited, restarted Verbum, was prompted to log in, and the sync worked fine immediately and from that point on. It seemed this locked out syncing because I had to log in again, it would have been nice if Faithlife would have warned people about this.

Juanita

https://community.logos.com/discussion/comment/749351#Comment_749351

This was also not the case, no new permissions were added.

I had never seen this before yesterday (the parts highlighted in yellow in the picture below):

Francis, I think you have a point--I had not seen this before yesterday. I balked at filling it out, re-started my computer and realized that I had to fill it out and authorize to get Logos to load.

Matthew C Jones

https://community.logos.com/discussion/comment/749386#Comment_749386

Francis, I think you have a point--I had not seen this before yesterday. I balked at filling it out, re-started my computer and realized that I had to fill it out and authorize to get Logos to load.

Could this be an effort to prevent software piracy?

https://community.logos.com/discussion/comment/749351#Comment_749351

This was also not the case, no new permissions were added.

I had never seen this before yesterday (the parts highlighted in yellow in the picture below):

Ah, I see what you mean and I stand corrected.

This is related to the new single sign-in feature we shipped for all our websites. Sign in should happen automatically for all of our sites unless your are not signed in on any of them.

The only time you would see this dialog is if you changed your password on a different device or explicitly signed out of the current site, or (as happened Monday night) we invalidated all tokens to fix a sign in bug (a bug we didn't intend to happen).

So, should you see the above dialog it's related to a new feature and the only new "permission" is to allow one Faithlife site to access another Faithlife site; this is required for single sign-in to work. This has nothing to do with software piracy, new regulations, etc.

https://community.logos.com/discussion/comment/749445#Comment_749445

This is related to the new single sign-in feature we shipped for all our websites. Sign in should happen automatically for all of our sites unless your are not signed in on any of them.

I like this new feature.

https://community.logos.com/discussion/comment/749555#Comment_749555

I like this new feature.

Me too, I will let the server team know.!

Matthias Chiang

https://community.logos.com/discussion/comment/749250#Comment_749250

I have he same problem as well. All my books in mobile iOS tablet/phone are gone!! This is not the first time Faithlife has invalidate the tokens. Every time when they force you to login, somehow for a group of people, the link to the downloaded books are removed and software simply crashed. I have to delete and reinstall and thereafter spent days to download my books so that I can bring with me to the fields that have with no data connection, Before Faithlife, I was using Logos without much problem. Now since the change to Faithlife, my faith is totally lost.

If Faithlife still doesn't address this bug or issue, it will come across to those customers that the process is deliberate and they are not interested in customer's feedback. Guess I will have to stop all future purchases, and channel them to other better bible softwares.

A sad day indeed.

https://community.logos.com/discussion/comment/749582#Comment_749582

Matthias,

Please see https://community.logos.com/forums/t/113006.aspx .

https://community.logos.com/discussion/comment/749582#Comment_749582

deleted on request.

https://community.logos.com/discussion/comment/749703#Comment_749703

Here is THE problem above all others I have- the sign in screen says it "wants permission" to use my data.

Charles,

What you mention here is unrelated to the subject of this post, and it makes things difficult when trying to find topics later on. Please create a new thread for this topic.

https://community.logos.com/discussion/comment/749703#Comment_749703

Dear Bruce: Just saw your post- thanks.
If its just single sign in, why didn't you guys just key-link the accounts?
I cant remember for certain but, it seems all my sign-in's are the same- I assumed that was coming from your end- sign in is the same for all Faithlife/Logos services.

Really confused here.

Just really hampered my ability to work at the conference- I had to get laptop and work in Accordance which- as you know- the resource selection isn't even close.

Suggestion would be: Anytime your going to do something on the back-end that can knock us out of work- send out emails, texts, put it on the forums ( whatever form of communication) with a date and time so we can be prepared and have a plan on our end.
For many of us- This is a tool, part of our Job.

Just a suggestion.

Grace and Peace

https://community.logos.com/discussion/comment/749706#Comment_749706

Removed as edit.

https://community.logos.com/discussion/comment/749706#Comment_749706

Suggestion would be: Anytime your going to do something on the back-end that can knock us out of work- send
out emails, texts, put it on the forums ( whatever form of communication) with a date and time so we can be prepared and have a plan on our end.

I think this idea has merit and is a fair request although I'm sure it is not that easy to always know whether work on the back-end might negatively impact things.

https://community.logos.com/discussion/comment/749759#Comment_749759

Suggestion would be: Anytime your going to do something on the back-end that can knock us out of work- send out emails, texts, put it on the forums ( whatever form of communication) with a date and time so we can be prepared and have a plan on our end.

I think this idea has merit and is a fair request although I'm sure it is not that easy to always know whether work on the back-end might negatively impact things.

Charles and Bruce -

I completely agree that all parties should (if possible) be notified in advance whenever anything might change that could affect customer productivity in any way. The reality is at times that simply *is not possible*. When a person falls down on the sidewalk clutching his chest at 11pm, the medics don't wait until 8am the next morning for a staff meeting to discuss the best course of action to help that person and then first notify his family about it.

Believe it or not, we *do* care and therefore took action right away on Monday night to solve a problem that might have affected tens of thousands of customers, but actually only affected a few dozen because we took immediate action to fix it. That immediate action caused the issue at hand.

Over the years Google's Gmail has gone down many times, without any notice. How is it possible that a company worth $367,600,000,000 could have their email service go down without notice? Mistakes happen, they didn't plan on it, and didn't announce it because they were too busy fixing it.

https://community.logos.com/discussion/comment/749778#Comment_749778

Believe it or not, we *do* care and therefore took action right away on Monday night to solve a problem that might have affected tens of thousands of customers, but actually only affected a few dozen because we took immediate action to fix it. That immediate action caused the issue at hand.

I totally understand what you are saying and it is very easy to not realize what it is like from your end. Issues do happen and they are often not foreseeable. I know you care and we appreciate it! Thank you.