{"id":67474,"date":"2024-06-19T14:28:34","date_gmt":"2024-06-19T14:28:34","guid":{"rendered":"https:\/\/logmeonce.com\/resources\/2023\/08\/10\/single-sign-on-vs-oauth\/"},"modified":"2024-06-19T18:57:58","modified_gmt":"2024-06-19T18:57:58","slug":"single-sign-on-vs-oauth","status":"publish","type":"post","link":"https:\/\/logmeonce.com\/resources\/single-sign-on-vs-oauth\/","title":{"rendered":"Single Sign On Vs OAuth"},"content":{"rendered":"<div class=\"336cb5b64765e27a1a6c1bb71b941f1a\" data-index=\"1\" style=\"float: none; margin:10px 0 10px 0; text-align:center;\">\n<script async src=\"https:\/\/pagead2.googlesyndication.com\/pagead\/js\/adsbygoogle.js?client=ca-pub-4830628043307652\"\r\n     crossorigin=\"anonymous\"><\/script>\r\n<!-- above content -->\r\n<ins class=\"adsbygoogle\"\r\n     style=\"display:block\"\r\n     data-ad-client=\"ca-pub-4830628043307652\"\r\n     data-ad-slot=\"5864845439\"\r\n     data-ad-format=\"auto\"\r\n     data-full-width-responsive=\"true\"><\/ins>\r\n<script>\r\n     (adsbygoogle = window.adsbygoogle || []).push({});\r\n<\/script>\n<\/div>\n<p>\u2064 Are you still confused\u2062 about \u2064Single Sign On Vs OAuth? Don\u2019t worry; we have all the answers here. Single Sign On (SSO) and OAuth are \u200btwo different methods of authentication used to control\u2062 access to protected resources\u200d on a network. SSO is a simpler method\u2063 of\u2064 authentication than OAuth, while OAuth provides more secure access to network resources. \u200cWhether you are a \u200bnew user who needs to\u2063 understand \u200bthe differences between Single Sign On and OAuth or a seasoned \u2063pro \u2062looking to\u200d optimize your \u200cuser authentication, this article will provide the information\u200d you need. We will cover the pros and\u200c cons\u200d of each, the implications\u200c of using \u2062each in \u2062an environment, and the best practices when implementing either.<\/p>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_77 counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/logmeonce.com\/resources\/single-sign-on-vs-oauth\/#1_What_Is_Single_Sign_On_and_OAuth\" >1. What Is Single Sign On and OAuth?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/logmeonce.com\/resources\/single-sign-on-vs-oauth\/#2_Comparing_SSO_and_OAuth_Benefits_and_Drawbacks\" >2. Comparing SSO and OAuth: Benefits and Drawbacks<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/logmeonce.com\/resources\/single-sign-on-vs-oauth\/#3_Making_the_Right_Choice_Single_Sign_%E2%80%8COn_%E2%80%8Dvs%E2%81%A4_OAuth\" >3. Making the Right Choice: Single Sign \u200cOn \u200dvs\u2064 OAuth<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/logmeonce.com\/resources\/single-sign-on-vs-oauth\/#4_Unlocking_the_Door_to_Security_Implementing_Single_Sign_On_or_OAuth\" >4. Unlocking the Door to Security: Implementing Single Sign On or OAuth<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/logmeonce.com\/resources\/single-sign-on-vs-oauth\/#Comparison_Between_Single_Sign_On_SSO_and_OAuth\" >Comparison Between Single Sign On (SSO) and OAuth<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/logmeonce.com\/resources\/single-sign-on-vs-oauth\/#Q_A\" >Q&amp;A<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/logmeonce.com\/resources\/single-sign-on-vs-oauth\/#Conclusion\" >Conclusion<\/a><\/li><\/ul><\/nav><\/div>\n<h2 id=\"1-what-is-single-sign-on-and-oauth\"><span class=\"ez-toc-section\" id=\"1_What_Is_Single_Sign_On_and_OAuth\"><\/span>1. What Is Single Sign On and OAuth?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><b>Single Sign On<\/b> \u2063(SSO)\u2064 is an identification system that allows users to access multiple services with\u2064 one set of credentials. It simplifies \u200bthe user experience since users don\u2019t have to remember multiple usernames and passwords. SSO\u200b works by redirecting a \u200buser\u2019s initial login request to an authentication \u2063provider, which \u200bwill authenticate the\u200c user and then redirect\u200b them to \u200btheir destination service.<\/p>\n<p><b>OAuth<\/b> \u200c is a secure open-standard\u2063 protocol that allows users to provide\u200c third-party applications with limited access to \u200ctheir resources without giving away their credentials. It has become popular among websites and\u200b applications \u2063that need to\u200d access data\u200b from other services. For \u2063example, if you want to post photos on\u200d Facebook from Instagram, OAuth will allow Instagram to authenticate you \u2062without\u2064 giving away your Facebook credentials.<\/p>\n<ul>\n<li>SSO is\u2062 an identification system that allows users to \u2063access multiple services with \u2063one set of credentials.<\/li>\n<li>OAuth \u200dis a \u200csecure open-standard\u2064 protocol that allows users to\u2062 provide third-party applications with limited access\u2064 to\u2062 their resources.<\/li>\n<li>OAuth is used to access data from other services without giving away credentials.<\/li>\n<\/ul>\n<h2 id=\"2-comparing-sso-and-oauth-benefits-and-drawbacks\"><span class=\"ez-toc-section\" id=\"2_Comparing_SSO_and_OAuth_Benefits_and_Drawbacks\"><\/span>2. Comparing SSO and OAuth: Benefits and Drawbacks<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Single sign-on (SSO) and OAuth are two\u200d popular methods \u200bof authentication.\u200d SSO is a centralized login system where users log in\u2064 once to access\u200d multiple\u2062 services, while OAuth is a decentralized system that allows users to grant third parties access to their\u200d data without compromising on security.<\/p>\n<p><b>Benefits of \u200bSSO<\/b><\/p>\n<p>SSO comes with benefits such as:<\/p>\n<ul>\n<li>Improved access control<\/li>\n<li>Enhanced user experience<\/li>\n<li>Cost efficiency<\/li>\n<\/ul>\n<p><b>Benefits \u200cof OAuth<\/b><\/p>\n<p>OADTH brings advantages to organizations such as:<\/p>\n<ul>\n<li>Multi-factor authentication<\/li>\n<li>Increased data security<\/li>\n<li>Better user\u2063 control<\/li>\n<\/ul>\n<p><b>Drawbacks\u2064 of SSO<\/b><\/p>\n<p>However,\u200c SSO comes with a few drawbacks as well such as:<\/p>\n<ul>\n<li>Security\u200c risks<\/li>\n<li>High cost\u2062 of infrastructure<\/li>\n<li>Difficulty in deploying\u200c across multiple platforms<\/li>\n<\/ul>\n<p><b>Drawbacks of OAuth <\/b><\/p>\n<p>OAuth also has some drawbacks such\u2063 as:\u2062<\/p>\n<ul>\n<li>High intrusion risk<\/li>\n<li>User-friendliness\u200b issues<\/li>\n<li>Limitations on sharing data across\u200b multiple\u2064 applications and\u2064 services<\/li>\n<\/ul>\n<h2 id=\"3-making-the-right-choice-single-sign-on-vs-oauth\"><span class=\"ez-toc-section\" id=\"3_Making_the_Right_Choice_Single_Sign_%E2%80%8COn_%E2%80%8Dvs%E2%81%A4_OAuth\"><\/span>3. Making the Right Choice: Single Sign \u200cOn \u200dvs\u2064 OAuth<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Whether you\u2019re\u200c making decisions for yourself or for your company, understanding the differences between \u2063Single Sign On (SSO) and\u200b OAuth\u200c is\u2063 critical. SSO and OAuth \u200bare \u200bauthentication methods\u2063 used to\u2062 control user access to\u200b websites, applications, \u2064and data.<\/p>\n<p>SSO provides a unified \u2064login option so users can access multiple applications simply by entering their username and password once. SSO systems\u2064 are easy to set up and free,\u2063 but with \u2062that comes limited security. On the other hand, OAuth is a secure authentication method that approves access\u2064 to third-party\u200d applications. To use \u200dOAuth, users are prompted to log\u200d in to\u200c the service with their username and password, then \u2063grant permission to access\u200c specific resources.<\/p>\n<p><strong>The Pros of SSO:<\/strong><\/p>\n<ul>\n<li>Simplifies the user\u200c experience<\/li>\n<li>Integrates with existing systems<\/li>\n<li>Lowers the risk of user password-sharing<\/li>\n<\/ul>\n<p><strong>The Benefits of OAuth:<\/strong><\/p>\n<ul>\n<li>Secure Access Control Authorization<\/li>\n<li>No user \u2063credentials are stored<\/li>\n<li>Less \u2064setup than SSO<\/li>\n<\/ul>\n<p>Choosing either SSO or OAuth will depend \u200con the \u2062security needs of the company. SSO is perfect \u2063for companies\u200c that \u2064are looking for\u200b convenience while\u200b OAuth is ideal for organizations that prioritize\u2064 increased security.<\/p>\n<h2 id=\"4-unlocking-the-door-to-security-implementing-single-sign-on-or-oauth\"><span class=\"ez-toc-section\" id=\"4_Unlocking_the_Door_to_Security_Implementing_Single_Sign_On_or_OAuth\"><\/span>4. Unlocking the Door to Security: Implementing Single Sign On or OAuth<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><b>Secure Login Access through Single Sign On or OAuth <\/b><\/p>\n<p>Single Sign On (SSO) and OAuth make\u200b it convenient for users to access multiple applications, websites, and services \u2062with \u200da single set of credentials. By using a single set of \u200bcredentials, these \u2063protocols \u200deliminate the need to recall multiple passwords or constantly type in logins. With SSO,\u2062 a \u2063single\u200c authentication\u200b window is provided \u2064for the\u200d user to enter their username and password, which is then vastly \u200bmore secure than multiple single access points. OAuth provides an additional layer of security\u200b by issuing and verifying access tokens and <a title=\"Single Sign On Vs OAuth\" href=\"https:\/\/logmeonce.com\/resources\/single-sign-on-vs-oauth\/\">utilizing software-server-based authentications<\/a>.<\/p>\n<p>With these protocols \u2062in place, \u200cno unauthorized access\u2062 can take place, \u200das the authentication process carefully monitors each login attempt. To further guarantee customer security,\u2062 the authentication process uses encrypted signatures, or digital signatures, to identify the\u200c users.\u200c With this secure layer of access and protection, users can log \u2064in safely without needing \u2064to constantly\u2064 reenter \u2063credentials. Enhanced security also allows more synchronized and secure access to data,\u2064 allowing authorized users to easily share information quickly and effectively.<\/p>\n<p>Single Sign On (SSO) and OAuth are both mechanisms that provide secure access to resources and applications. SSO is a process in which a user can access multiple applications with a single set of login credentials, while OAuth is an authorization framework that allows third-party applications to access a user&#8217;s resources without sharing the user&#8217;s login credentials. In SSO, the service provider acts as the identity provider, granting access to resources based on the user&#8217;s credentials.<\/p>\n<p>On the other hand, OAuth 2.0 involves an authorization server that controls the access to resources on behalf of the user. This allows for seamless access to resources across different platforms, including mobile applications, social logins, and third-party apps. OAuth is considered more secure as it eliminates the need to share login credentials with third-party applications, reducing the risk of security vulnerabilities.<\/p>\n<p>It also provides a standardized and industry-supported protocol for secure authorization and access management. In contrast, SSO systems such as SAML 2.0 require the exchange of secure assertions in XML format to grant access between apps, which may not be as efficient as OAuth in modern applications. Overall, both SSO and OAuth play crucial roles in identity and access management, with OAuth being the preferred choice for secure and seamless access delegation in today&#8217;s digital landscape.<\/p>\n<p>In today&#8217;s digital age, the ease of access to various online services and applications has become an essential aspect of our daily lives. However, with increased access comes the need for robust security measures to protect user credentials and ensure data privacy. Single Sign-On (SSO) and OAuth are two popular authentication and authorization methods that play a crucial role in enabling secure access to resources while simplifying the user experience.<\/p>\n<p><a href=\"http:\/\/en.wikipedia.org\/wiki\/XML\" target=\"_blank\" rel=\"noopener nofollow\">Single Sign-On<\/a> (SSO) is a method that allows users to access multiple applications or services using a single set of login credentials. This eliminates the need for users to remember and enter different login credentials for each service provider they interact with. In the SSO process, the user&#8217;s identity is verified by an identity provider (IdP) once, and the user is granted access to various resources provided by service providers without the need to re-enter their credentials.<\/p>\n<p>SSO not only streamlines the login process for users but also enhances security by reducing the risk of password fatigue and potential security vulnerabilities associated with using multiple passwords across various platforms. It also improves user productivity by simplifying access to resources and reducing the time spent on authentication processes.<\/p>\n<p>OAuth (Open Authorization) is an industry-standard protocol that enables secure authorization and access to resources on behalf of a user without sharing their login credentials. OAuth is commonly used in scenarios where a user grants access to their resources on one service (called the authorization server) to another service (called the resource server) without revealing their login details.<\/p>\n<p>OAuth 2.0, the latest version of OAuth, has become widely adopted for enabling secure authorization flows in modern applications, especially mobile apps and social logins. It provides a flexible and secure framework for delegating access to third-party applications without compromising user credentials. With OAuth, users can grant temporary access to their data or resources to third-party apps, enhancing user control over their information while maintaining security.<\/p>\n<p>While both SSO and OAuth aim to simplify access to resources and enhance security, there are key differences between the two methods. SSO focuses on authentication, allowing users to log in once and access multiple services seamlessly. On the other hand, OAuth is primarily an authorization protocol, enabling users to grant access to their resources to third-party apps without sharing their credentials.<\/p>\n<p>SSO relies on a centralized identity provider (IdP) for authentication, while OAuth involves an authorization server that oversees the access control decisions. SSO is commonly used in enterprise applications and cloud platforms to streamline user access, while OAuth is prevalent in scenarios requiring secure access delegation to third-party applications, such as social media platforms and mobile devices.<\/p>\n<p>In conclusion, both Single Sign-On and OAuth play crucial roles in enabling secure access to resources and simplifying the user experience in today&#8217;s digital landscape. While SSO focuses on seamless authentication across multiple services, OAuth provides a secure authorization framework for granting access to third-party apps without exposing user credentials. By understanding the differences and benefits of these authentication and authorization methods, organizations can implement robust identity and access management solutions that prioritize security and user convenience.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Comparison_Between_Single_Sign_On_SSO_and_OAuth\"><\/span>Comparison Between Single Sign On (SSO) and OAuth<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<table>\n<tbody>\n<tr>\n<th><\/th>\n<th>Single Sign On (SSO)<\/th>\n<th>OAuth<\/th>\n<\/tr>\n<tr>\n<td>Definition<\/td>\n<td>Identification system allowing access to multiple services with one set of credentials<\/td>\n<td>Secure protocol enabling third-party apps access to resources without sharing user credentials<\/td>\n<\/tr>\n<tr>\n<td>Focus<\/td>\n<td>Authentication method<\/td>\n<td>Authorization framework<\/td>\n<\/tr>\n<tr>\n<td>Key Component<\/td>\n<td>Centralized Identity Provider (IdP)<\/td>\n<td>Authorization Server<\/td>\n<\/tr>\n<tr>\n<td>Usage<\/td>\n<td>Enterprise applications, cloud platforms<\/td>\n<td>Social media platforms, mobile devices<\/td>\n<\/tr>\n<tr>\n<td>Advantages<\/td>\n<td>Convenience, enhanced security, improved user experience<\/td>\n<td>Increased data security, better user control, multi-factor authentication<\/td>\n<\/tr>\n<tr>\n<td>Disadvantages<\/td>\n<td>Security risks, high infrastructure cost, deployment challenges<\/td>\n<td>High intrusion risk, user-friendliness issues, limited data sharing<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2 id=\"qa\"><span class=\"ez-toc-section\" id=\"Q_A\"><\/span>Q&amp;A<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Q: What is the difference between Single Sign-On (SSO) and OAuth?<br \/>\nA: Single Sign-On (SSO) is a method that allows users to access multiple applications with a single set of login credentials, typically managed by a central Identity Provider (IdP). On the other hand, OAuth is an authorization protocol that enables a user to grant access to their resources on one site to another site without sharing their login credentials.<\/p>\n<p>Q: How does OAuth work in the context of accessing resources?<br \/>\nA: In OAuth, the user grants access to their resources on a Resource Server (such as a social media platform) to a third-party app through an Authorization Server. This process is facilitated by an authorization flow, which allows the third-party app to access the user&#8217;s data without exposing their login credentials.<\/p>\n<p>Q: What are some common use cases for OAuth in modern applications?<br \/>\nA: OAuth is commonly used in mobile applications, desktop applications, and cloud applications to enable secure access to user data without requiring users to share their login details. It is also often used for social logins and to access APIs in a secure and standardized way.<\/p>\n<p>Q: What are the key differences between SSO and OAuth?<br \/>\nA: The main difference between SSO and OAuth is that SSO focuses on managing user authentication through a single set of login credentials, while OAuth is primarily used for authorization and access control between different applications without sharing user credentials.<\/p>\n<p>Q: How does OAuth enhance security in accessing user data?<br \/>\nA: OAuth utilizes secure authorization processes and protocols such as OAuth 2.0 and OpenID Connect to ensure that access to user data is managed in a secure and standardized manner. It also allows users to control the level of access granted to third-party apps, enhancing privacy and security.<\/p>\n<h2 id=\"outro\"><span class=\"ez-toc-section\" id=\"Conclusion\"><\/span>Conclusion<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>In\u200c conclusion, Single\u2064 Sign-On and OAuth\u2064 are\u200b two popular methods \u2064for authenticating users. Creating a FREE\u200b LogMeOnce account is one of the\u200c best solutions for secure access and single sign on to all your\u2063 web applications\u200b and services. This security\u2064 technology is so powerful and optimized that you can forget all your \u200bworries of securely logging\u2062 into multiple online services and accounts\u200c with\u2062 one single password or token. With <a href=\"https:\/\/logmeonce.com\/\">LogMeOnce<\/a>, you can stay assured of the fact that you are using the latest single sign-on technology and single\u2062 sign on security protocols compatible with your existing OAuth and\u200d SSO\u200b infrastructures.\u200c With its robust single sign on (SSO) and \u200bOAuth security \u200dfeatures, LogMeOnce\u2064 is the ultimate key to\u200c convenient and secure online service \u2063access today. Keywords: \u200cSingle Sign On(SSO),\u2063 OAuth.<\/p>\n\n<div style=\"font-size: 0px; height: 0px; line-height: 0px; margin: 0; padding: 0; clear: both;\"><\/div>","protected":false},"excerpt":{"rendered":"<p>\u2064 Are you still confused\u2062 about \u2064Single Sign On Vs OAuth? Don\u2019t worry; we have all the answers here. Single Sign On (SSO) and OAuth are \u200btwo different methods of authentication used to control\u2062 access to protected resources\u200d on a network. SSO is a simpler method\u2063 of\u2064 authentication than OAuth, while OAuth provides more secure [&hellip;]<\/p>\n","protected":false},"author":27,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[19736],"tags":[1294,8770,3604,14517,781,8032],"class_list":["post-67474","post","type-post","status-publish","format-standard","hentry","category-single-sign-on","tag-authentication","tag-authorization","tag-identity-management","tag-oauth","tag-security","tag-single-sign-on"],"acf":[],"_links":{"self":[{"href":"https:\/\/logmeonce.com\/resources\/wp-json\/wp\/v2\/posts\/67474","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/logmeonce.com\/resources\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/logmeonce.com\/resources\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/logmeonce.com\/resources\/wp-json\/wp\/v2\/users\/27"}],"replies":[{"embeddable":true,"href":"https:\/\/logmeonce.com\/resources\/wp-json\/wp\/v2\/comments?post=67474"}],"version-history":[{"count":0,"href":"https:\/\/logmeonce.com\/resources\/wp-json\/wp\/v2\/posts\/67474\/revisions"}],"wp:attachment":[{"href":"https:\/\/logmeonce.com\/resources\/wp-json\/wp\/v2\/media?parent=67474"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/logmeonce.com\/resources\/wp-json\/wp\/v2\/categories?post=67474"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/logmeonce.com\/resources\/wp-json\/wp\/v2\/tags?post=67474"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}