English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Tools annual

Global: Zendy Free Plan

Global: Zendy Tools monthly

Global: Zendy Plus monthly

Usable and secure authentication on the web and beyond is mission-critical.While password-based authentication is still widespread, users have troubledealing with potentially hundreds of online accounts and their passwords.Alternatives or extensions such as multi-factor authentication have their ownchallenges and find only limited adoption. Finding the right balance betweensecurity and usability is challenging for developers. Previous work found thatdevelopers use online resources to inform security decisions when writing code.Similar to other areas, lots of authentication advice for developers isavailable online, including blog posts, discussions on Stack Overflow, researchpapers, or guidelines by institutions like OWASP or NIST.  We are the first to explore developer advice on authentication that affectsusable security for end-users. Based on a survey with 18 professional webdevelopers, we obtained 406 documents and qualitatively analyzed 272 containedpieces of advice in depth. We aim to understand the accessibility and qualityof online advice and provide insights into how online advice might contributeto (in)secure and (un)usable authentication. We find that advice is scatteredand that finding recommendable, consistent advice is a challenge fordevelopers, among others. The most common advice is for password-basedauthentication, but little for more modern alternatives. Unfortunately, manypieces of advice are debatable (e.g., complex password policies), outdated(e.g., enforcing regular password changes), or contradicting and might lead tounusable or insecure authentication. Based on our findings, we makerecommendations for developers, advice providers, official institutions, andacademia on how to improve online advice for developers.

"Make Them Change it Every Week!": A Qualitative Exploration of Online Developer Advice on Usable and Secure Authentication