![]() ![]() ![]() So I've noticed a sharp incline in inbound spam recently and I noticed a very unusual new one.It has a few very specific characteristics that make it stand out from normal spam messages:1 - it contains real email reply threads2 - it contains real names of. Reply Threads + OneDrive link + file PWD Security Spark! Pro series – 25th March 2022 Spiceworks Originalsįor other uses, see Friday (disambiguation).So I vote: Let's hear more about what you are trying to accomplish with your policy and maybe we can suggest a way forward that you AND your users will tolerate :) Every other poster here is correct- single sign-on isn't born out of laziness but rather the need to keep users from going insane. (It's an unavoidable consequence of moving from static to changing credentials) In other words, the opposite direction you're trying to go. (For example, your file server can demand that a valid 2-factor logon token be presented before allowing access.) In this way, you could contrive to make the file server pop up a credential prompt when stale (or no) OTP is presented.īut usually our customers have to put in some effort to configure the solution to minimize how often credentials are needed, and improve single sign-on. You can specify when credentials need to be entered and what they can be used for. If what you are trying to do is prevent stale credentials from being perpetually re-used, then the ultimate solution is something like (ahem, our product) AuthLite, that teaches the domain how to understand one-time passcodes. The appropriate solution might be something completely different than what you envision. I also want to know the answer to this! Instead of commenting on the technical answer or advising against it, let's try to actually figure out what the underlying goal is. What are you hoping to accomplish with this? ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |