# AOL Published articles for AOL. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Innovating on Authentication Standards DevFeed: [Innovating on Authentication Standards]() Original publisher: [Read original article]() Author: mikesefanov Published: 2018-06-25T13:59:44Z Content type: article Language: en Sources: [Yahoo]() Topics: [Authentication](), [OAuth 2.0](), [Mobile]() Tags: [aol](), [authentication](), [identity](), [mobile](), [mobile-apps](), [oauth2](), [standards](), [yahoo](), [yahoo-engineering]() ### AI overview Yahoo and AOL describe how they used existing identity standards to address migrating identities in mobile apps from a legacy provider to the Oath identity platform. The article focuses on using OAuth 2.0 Token Exchange so apps can move between identity providers without requiring users to re-enter credentials. ### Source excerpt yahoodevelopers: By George Fletcher and Lovlesh Chhabra When Yahoo and AOL came together a year ago as a part of the new Verizon subsidiary Oath, we took on the challenge of unifying their identity platforms based on current identity standards. Identity standards have been a critical part of the Internet ecosystem over the last 20+ years. From single-sign-on and identity federation with SAML; to the newer identity protocols including OpenID Connect, OAuth2, JOSE, and SCIM (to name a few); to the explorations of "self-sovereign identity" based on distributed ledger technologies; standards have played a key role in providing a secure identity layer for the Internet. As we navigated this journey, we ran across a number of different use cases where there was either no standard or no best practice available for our varied and complicated needs. Instead of creating entirely new standards to solve our problems, we found it more productive to use existing standards in new ways. One such use case arose when we realized that we needed to migrate the identity stored in mobile apps from the legacy identity provider to the new Oath identity platform. For most browser (mobile or desktop) use cases, this doesn't present a huge problem; some DNS magic and HTTP redirects and the user will sign in at the correct endpoint. Also it's expected for users accessing services via their browser to have to sign in now and then. However, for mobile applications it's a completely different story. The normal user pattern for mobile apps is for the user to sign in (via OpenID Connect or OAuth2) and for the app to then be issued long-lived tokens (well, the refresh token is long lived) and the user never has to sign in again on the device (entering a password on the device is NOT a good experience for the user). So the issue is, how do we allow the mobile app to move from one identity provider to another without the user having to re-enter their credentials? The solution came from researching what ## Accessing Yahoo and AOL Mail Features Through IMAP DevFeed: [Accessing Yahoo and AOL Mail Features Through IMAP]() Original publisher: [Read original article]() Author: marcelatoath Published: 2018-05-18T16:19:38Z Content type: tutorial Language: en Sources: [Yahoo]() Topics: [Protocol (disambiguation)](), [servers](), [client](), [openssl]() Tags: [aol](), [developers](), [openssl](), [protocol](), [server](), [yahoo](), [yahoo-engineering]() ### AI overview This tutorial explains how developers can access Yahoo and AOL Mail metadata such as DECOS and THREADID through IMAP. It demonstrates an IMAP command sequence using openssl to connect, authenticate, list folders, select the inbox, and search for message UIDs. ### Source excerpt USE IMAP TO ACCESS SOME UNIQUE FEATURES By Libby Lin, Principal Product Manager Well, we actually won't show you how we create the magic in our big OATH consumer mail factory. But nevertheless we wanted to share how interested developers could leverage some of our unique features we offer for our Yahoo and AOL Mail customers. To drive experiences like our travel and shopping smart views or message threading, we tag qualified mails with something we call DECOS and THREADID. While we will not indulge in explaining how exactly we use them internally, we wanted to share how they can be used and accessed through IMAP. So let's just look at a sample IMAP command chain. We'll just assume that you are familiar with the IMAP protocol at this point and you know how to properly talk to an IMAP server. So here's how you would retrieve DECO and THREADIDs for specific messages: 1. CONNECT openssl s_client -crlf -connect imap.mail.yahoo.com:993 2. LOGIN a login username password a OK LOGIN completed 3. LIST FOLDERS a list "" "*" * LIST (\Junk \HasNoChildren) "/" "Bulk Mail" * LIST (\Archive \HasNoChildren) "/" "Archive" * LIST (\Drafts \HasNoChildren) "/" "Draft" * LIST (\HasNoChildren) "/" "Inbox" * LIST (\HasNoChildren) "/" "Notes" * LIST (\Sent \HasNoChildren) "/" "Sent" * LIST (\Trash \HasChildren) "/" "Trash" * LIST (\HasNoChildren) "/" "Trash/l2" * LIST (\HasChildren) "/" "test level 1" * LIST (\HasNoChildren) "/" "test level 1/nestedfolder" * LIST (\HasNoChildren) "/" "test level 1/test level 2" * LIST (\HasNoChildren) "/" "&T2BZfXso-" * LIST (\HasNoChildren) "/" "&gQKAqk7WWr12hA-" a OK LIST completed 4.SELECT FOLDER a select inbox * 94 EXISTS * 0 RECENT * OK [UIDVALIDITY 1453335194] UIDs valid * OK [UIDNEXT 40213] Predicted next UID * FLAGS (\Answered \Deleted \Draft \Flagged \Seen $Forwarded $Junk $NotJunk) * OK [PERMANENTFLAGS (\Answered \Deleted \Draft \Flagged \Seen $Forwarded $Junk $NotJunk)] Permanent flags * OK [HIGHESTMODSEQ 205] a OK [READ-WRITE] SELECT completed; ## Yahoo and AOL Mail Begin Serving Images Through Secure Proxy Servers DevFeed: [Yahoo and AOL Mail Begin Serving Images Through Secure Proxy Servers]() Original publisher: [Read original article]() Author: marcelatoath Published: 2018-03-20T14:54:05Z Content type: release Language: en Sources: [Yahoo]() Topics: [Security](), [Server](), [App]() Tags: [android](), [aol](), [applications](), [browser](), [ios](), [secure-images](), [security](), [servers](), [yahoo-engineering]() ### AI overview Yahoo and AOL mail products are beginning to serve email images through secure proxy servers to improve speed and security and reduce phishing and scam risks. The change applies to desktop and mobile applications on iOS and Android, while most image-based open tracking remains supported. ### Source excerpt oath-postmaster: By Marcel Becker The mail team at OATH is busy integrating Yahoo and AOL technology to deliver an even better experience across all our consumer mail products. While privacy and security are top priority for us, we also want to improve the experience and remove unnecessary clutter across all of our products. Starting this week we will be serving images in mails via our own secure proxy servers. This will not only increase speed and security in our own mail products and reduce the risk of phishing and other scams, but it will also mean that our users don't have to fiddle around with those "enable images" settings. Messages and inline images will now just show up as originally intended. We are aware that commercial mail senders are relying on images (so-called pixels) to track delivery and open rates. Our proxy solution will continue to support most of these cases and ensure that true mail opens are recorded. For senders serving dynamic content based on the recipient's location (leveraging standard IP-based browser and app capabilities) we recommend falling back on other tools and technologies which do not rely on IP-based targeting. All of our consumer mail applications (Yahoo and AOL) will benefit from this change. This includes our desktop products as well as our mobile applications across iOS and Android. If you have any feedback or want to discuss those changes with us personally, just send us a note to mail-questions@oath.com.