{"id":9213,"date":"2021-06-19T18:28:15","date_gmt":"2021-06-19T15:28:15","guid":{"rendered":"https:\/\/kifarunix.com\/?p=9213"},"modified":"2024-03-18T20:36:18","modified_gmt":"2024-03-18T17:36:18","slug":"configure-sssd-for-ldap-authentication-on-rocky-linux-8","status":"publish","type":"post","link":"https:\/\/kifarunix.com\/configure-sssd-for-ldap-authentication-on-rocky-linux-8\/","title":{"rendered":"Configure SSSD for LDAP Authentication on Rocky Linux 8"},"content":{"rendered":"\n<p>In this guide, we are going to demonstrate how to configure SSSD for LDAP Authentication on Rocky Linux 8. In our previous guides, we have covered how to install and setup OpenLDAP on Rocky Linux 8 as well how to configure SUDO via OpenLDAP. See the links below;<\/p>\n\n\n\n<p><a href=\"https:\/\/kifarunix.com\/install-and-setup-openldap-on-rocky-linux-8\/\" target=\"_blank\" rel=\"noreferrer noopener\">Install and Setup OpenLDAP on Rocky Linux 8<\/a><\/p>\n\n\n\n<p><a rel=\"noreferrer noopener\" href=\"https:\/\/kifarunix.com\/how-to-configure-sudo-via-openldap-server\/\" target=\"_blank\">How to Configure SUDO via OpenLDAP Server<\/a><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Configuring SSSD for LDAP Authentication<\/h2>\n\n\n\n<p><a href=\"https:\/\/docs.pagure.org\/SSSD.sssd\/\" target=\"_blank\" rel=\"noreferrer noopener\">SSSD<\/a>&nbsp;is an acronym for System Security Services Daemon. It provides access to different identity and authentication providers.<\/p>\n\n\n\n<p>In this demo, we are using OpenLDAP as our directory as well identity management server.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Run system update<\/h3>\n\n\n\n<p>To update your system packages, execute the command below;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>dnf update<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Install SSSD on Rocky Linux 8<\/h3>\n\n\n\n<p>Once the system update is done, proceed to install SSSD and other SSSD tools.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>dnf install sssd sssd-tools<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Configure LDAP Authentication via SSSD<\/h3>\n\n\n\n<p>Next, configure SSSD to allow authentication to your local system via OpenLDAP.<\/p>\n\n\n\n<p>SSSD doesn\u2019t usually ship with any default configuration file. As such you need to create and configure it manually.<\/p>\n\n\n\n<p>Paste the content below into&nbsp;<strong>sssd.conf<\/strong>&nbsp;file.<\/p>\n\n\n\n<p>Be sure to make the relevant substitutions replacing your domain components as well as the BIND DN password appropriately.<\/p>\n\n\n\n<pre class=\"scroll-box\"><code>\ncat > \/etc\/sssd\/sssd.conf << 'EOL'\n[sssd]\nservices = nss, pam, sudo\nconfig_file_version = 2\ndomains = default\n\n[sudo]\n\n[nss]\n\n[pam]\noffline_credentials_expiration = 60\n\n[domain\/default]\nldap_id_use_start_tls = True\ncache_credentials = True\nldap_search_base = dc=ldapmaster,dc=kifarunix-demo,dc=com\nid_provider = ldap\nauth_provider = ldap\nchpass_provider = ldap\naccess_provider = ldap\nsudo_provider = ldap\nldap_uri = ldap:\/\/ldapmaster.kifarunix-demo.com\nldap_default_bind_dn = cn=readonly,ou=system,dc=ldapmaster,dc=kifarunix-demo,dc=com\nldap_default_authtok = P@ssWOrd\nldap_tls_reqcert = demand\nldap_tls_cacert = \/etc\/pki\/tls\/cacert.crt\nldap_tls_cacertdir = \/etc\/pki\/tls\nldap_search_timeout = 50\nldap_network_timeout = 60\nldap_sudo_search_base = ou=SUDOers,dc=ldapmaster,dc=kifarunix-demo,dc=com\nldap_access_order = filter\nldap_access_filter = (objectClass=posixAccount)\nEOL\n<\/code><\/pre>\n\n\n\n<p>Save and quit the configuration files. Be sure to make relevant changes accordingly.<\/p>\n\n\n\n<p>Note that we have also configured our OpenLDAP server to provide sudo rights as shown by the configurations;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>services = nss, pam, <strong>sudo<\/strong>\n...\n\n<strong>[sudo]<\/strong>\n...\n\n<strong>ldap_sudo_search_base = ou=SUDOers,dc=ldapmaster,dc=kifarunix-demo,dc=com<\/strong><\/code><\/pre>\n\n\n\n<p><strong>If you are not using OpenLDAP for sudo rules<\/strong>, you can remove these configurations.<\/p>\n\n\n\n<p>Next, download the OpenLDAP server CA certificate and store it on the file specified by the&nbsp;<code>ldap_tls_cacert<\/code>&nbsp;directive on the sssd.conf file above.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>openssl s_client -connect ldapmaster.kifarunix-demo.com:636 -showcerts &lt; \/dev\/null | openssl x509 -text<\/code><\/pre>\n\n\n\n<p>Copy the certificate and paste it on the&nbsp;<strong><code>\/etc\/pki\/tls\/cacert.crt<\/code><\/strong>.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>vim \/etc\/pki\/tls\/cacert.crt<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>-----BEGIN CERTIFICATE-----\nMIIFxzCCA6+gAwIBAgIUV+l4aOvMCLlNQRKOpt9YfxcxA8MwDQYJKoZIhvcNAQEL\nBQAwczELMAkGA1UEBhMCS0UxEDAOBgNVBAgMB05haXJvYmkxDDAKBgNVBAcMA05h\n...\n...\n5deiMlJkrYv7wZ0prq0QO5lduGBuD9UJvRa8LBV0GEAiHZL5PJOnREHObbAH907E\neixIJpkcC4wguMaXDNqIv6WGdQtRUyIP8tdByXYJGrbRW0K\/K9qEaIZhJiAES1Qy\n8U96RdYBpLvDctRch1kIfvnAVffTxmObAGI9n64O89p48kocJwNI\/XQNRg==\n-----END CERTIFICATE-----<\/code><\/pre>\n\n\n\n<p>Next, open the&nbsp;<code>\/etc\/openldap\/ldap.conf<\/code>&nbsp;configuration file and configure it as follows;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>vim \/etc\/openldap\/ldap.conf<\/code><\/pre>\n\n\n\n<p>Basically, you need to define the location of the CA certificate, the OpenLDAP search base, the URI and if you are providing SUDO via OpenLDAP, the SUDOers base.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>BASE    dc=ldapmaster,dc=kifarunix-demo,dc=com\nURI     ldaps:\/\/ldapmaster.kifarunix-demo.com:636\nSUDOERS_BASE    ou=SUDOers,dc=ldapmaster,dc=kifarunix-demo,dc=com\n...\n...\nTLS_CACERT      \/etc\/pki\/tls\/cacert.crt\n...<\/code><\/pre>\n\n\n\n<p>Save and quit the configuration file.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Configure Name Service Switch and PAM on Rocky Linux 8<\/h3>\n\n\n\n<p>Next, you need to update the NSS and PAM to use SSSD to manage authentication resources.<\/p>\n\n\n\n<p>In previous versions of CentOS, you would use tools like&nbsp;<code><strong>authconfig<\/strong><\/code>&nbsp;but this has since been replaced by tools like&nbsp;<code><strong>authselect<\/strong><\/code>.<\/p>\n\n\n\n<p><code>Authselect<\/code>&nbsp;is a utility that simplifies the configuration of user authentication&nbsp;especially while using SSSD for authentication.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Configure SSSD Profile<\/h4>\n\n\n\n<p>Authselect command when used to create an SSSD profile, will basically modify these files;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\/etc\/pam.d\/system-auth<\/li>\n\n\n\n<li>\/etc\/pam.d\/password-auth<\/li>\n\n\n\n<li>\/etc\/pam.d\/fingerprint-auth<\/li>\n\n\n\n<li>\/etc\/pam.d\/smartcard-auth<\/li>\n\n\n\n<li>\/etc\/pam.d\/postlogin<\/li>\n\n\n\n<li>\/etc\/nsswitch.conf<\/li>\n<\/ul>\n\n\n\n<p>Therefore, make a back up of these files just in case things don\u2019t work out. Once you have backed up these files, remove them.<\/p>\n\n\n\n<p>Create an SSSD profile. This command will succeed only of you have removed the files above.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>authselect select sssd<\/code><\/pre>\n\n\n\n<p>Otherwise, you can overwrite the files by adding the&nbsp;<code>--force<\/code>&nbsp;option.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>authselect select sssd --force<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>Backup stored at \/var\/lib\/authselect\/backups\/2021-06-19-09-55-01.BaMqgB\nProfile \"sssd\" was selected.\nThe following nsswitch maps are overwritten by the profile:\n- passwd\n- group\n- netgroup\n- automount\n- services\n\nMake sure that SSSD service is configured and enabled. See SSSD documentation for more information.<\/code><\/pre>\n\n\n\n<p>Next, for the system to fetch sudo rights from SSSD\/OpenLDAP, edit the&nbsp;<code>\/etc\/nsswitch.conf<\/code>&nbsp;to include the line below.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>sudoers:    files sss<\/code><\/pre>\n\n\n\n<p>You can simply echo the line into the configuration file as shown below;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>echo \"sudoers:    files sss\" &gt;&gt; \/etc\/nsswitch.conf<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Configure Automatic Home Directory Creation<\/h3>\n\n\n\n<p>To enable automatic home directory creation for user upon first login, you need to install the&nbsp;<code><strong>oddjob-mkhomedir<\/strong><\/code>, which provides the&nbsp;<code><strong>pam_oddjob_mkhomedir<\/strong><\/code>&nbsp;module to create a home directory for a user at login-time.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>dnf install oddjob-mkhomedir<\/code><\/pre>\n\n\n\n<p>Start and enable oddjobd to run on system boot.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>systemctl enable --now oddjobd<\/code><\/pre>\n\n\n\n<p>Load the&nbsp;<code><strong>pam_oddjob_mkhomedir<\/strong><\/code>&nbsp;module in PAM auth file&nbsp;<code>\/etc\/pam.d\/system-auth<\/code>&nbsp;to enable auto home directory creation.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>echo \"session optional pam_oddjob_mkhomedir.so skel=\/etc\/skel\/ umask=0022\" &gt;&gt; \/etc\/pam.d\/system-auth<\/code><\/pre>\n\n\n\n<p>Restart oddjobd.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>systemctl restart oddjobd<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Running SSSD<\/h3>\n\n\n\n<p>Before you can start SSSD, you need to check configuration for any typos or permissions;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>sssctl config-check<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>File ownership and permissions check failed. Expected root:root and 0600.<\/code><\/pre>\n\n\n\n<p>As per the check output, set the read\/write access to&nbsp;<code>\/etc\/sssd\/<\/code>&nbsp;for the owner (root).<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>chown -R root: \/etc\/sssd<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>chmod 600 -R \/etc\/sssd<\/code><\/pre>\n\n\n\n<p>The configuration is now done. Start and enable SSSD to run on system boot.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>systemctl enable --now sssd<\/code><\/pre>\n\n\n\n<p>Check the status.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>systemctl status sssd<\/code><\/pre>\n\n\n\n<pre class=\"scroll-box\"><code>\n\u25cf sssd.service - System Security Services Daemon\n   Loaded: loaded (\/usr\/lib\/systemd\/system\/sssd.service; enabled; vendor preset: enabled)\n   Active: active (running) since Sat 2021-06-19 05:43:33 EDT; 13min ago\n Main PID: 892 (sssd)\n    Tasks: 3 (limit: 11256)\n   Memory: 12.0M\n   CGroup: \/system.slice\/sssd.service\n           \u251c\u2500892 \/usr\/sbin\/sssd -i --logger=files\n           \u251c\u2500941 \/usr\/libexec\/sssd\/sssd_be --domain implicit_files --uid 0 --gid 0 --logger=files\n           \u2514\u2500946 \/usr\/libexec\/sssd\/sssd_nss --uid 0 --gid 0 --logger=files\n\nJun 19 05:43:17 localhost.localdomain systemd[1]: Starting System Security Services Daemon...\nJun 19 05:43:28 localhost.localdomain sssd[sssd][892]: Starting up\nJun 19 05:43:29 localhost.localdomain sssd[be[implicit_files]][941]: Starting up\nJun 19 05:43:32 localhost.localdomain sssd[nss][946]: Starting up\nJun 19 05:43:33 localhost.localdomain systemd[1]: Started System Security Services Daemon.\n<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Test OpenLDAP Authentication via SSSD<\/h3>\n\n\n\n<p>Assuming that you have already created your OpenLDAP users and groups ( if not check our guide on&nbsp;<a rel=\"noreferrer noopener\" href=\"https:\/\/kifarunix.com\/install-and-setup-openldap-on-centos-8\/\" target=\"_blank\">creating OpenLDAP Users and Groups<\/a>), verify that you can login.<\/p>\n\n\n\n<p>First, confirm that you can see your LDAP username on your system using&nbsp;<code>id<\/code>&nbsp;command.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>id johndoe<\/code><\/pre>\n\n\n\n<p>You should get an entry similar to below. Note that username and UID and GUID may vary depending on your OpenLDAP settings;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>uid=10000(johndoe) gid=10000(johndoe) groups=10000(johndoe)<\/code><\/pre>\n\n\n\n<p>If you cant get the above output, be sure to check OpenLDAP syslog logs (slapd.log, as per our setup guide) as well as <strong><code>sssd<\/code><\/strong> logs.<\/p>\n\n\n\n<p>Otherwise, you can restart sssd;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>systemctl restart sssd<\/code><\/pre>\n\n\n\n<p>Check user again using&nbsp;<code>id<\/code>&nbsp;command.<\/p>\n\n\n\n<p>If all is well, Perform a local ssh authentication to test your LDAP authentication.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>ssh -l johndoe localhost<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>The authenticity of host 'localhost (::1)' can't be established.\nECDSA key fingerprint is SHA256:WuslT7dUhvAkOndw1DZEgJ46bzVUbzewVU9RYcWmPg8.\nAre you sure you want to continue connecting (yes\/no\/&#91;fingerprint])? yes\nWarning: Permanently added 'localhost' (ECDSA) to the list of known hosts.\njohndoe@localhost's password: <strong>ENTER USER's LDAP Password<\/strong><\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Verify that you got sudo rights.<\/h3>\n\n\n\n<p>First, if you have assigned the user sudo rights, you can check by running the command below on your OpenLDAP server. Replace the domain components accordingly.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>export SUDOERS_BASE=ou=SUDOers,dc=ldapmaster,dc=kifarunix-demo,dc=com<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>ldapsearch -b \"$SUDOERS_BASE\" -D cn=admin,dc=ldapmaster,dc=kifarunix-demo,dc=com -W -x<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>...\n# sudo, SUDOers, ldapmaster.kifarunix-demo.com\ndn: cn=sudo,ou=SUDOers,dc=ldapmaster,dc=kifarunix-demo,dc=com\nobjectClass: top\nobjectClass: sudoRole\ncn: sudo\nsudoUser: johndoe\nsudoHost: ALL\nsudoRunAsUser: ALL\nsudoCommand: ALL\n...<\/code><\/pre>\n\n\n\n<p>Next, on the LDAP client with SSSD running already, try to list the user's sudo rights.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>[johndoe@localhost ~]$ sudo -l<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>We trust you have received the usual lecture from the local System\nAdministrator. It usually boils down to these three things:\n\n    #1) Respect the privacy of others.\n    #2) Think before you type.\n    #3) With great power comes great responsibility.\n\n&#91;sudo] password for johndoe: \n<strong>Sorry, user johndoe may not run sudo on localhost.<\/strong><\/code><\/pre>\n\n\n\n<p>Well, if you get the error, <strong>Sorry, user johndoe may not run sudo on localhost.<\/strong>, <strong>then exit as standard user and restart SSSD;<\/strong><\/p>\n\n\n\n<p>Once you restart SSSD, check the sudo rights again;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>sudo -l<\/code><\/pre>\n\n\n\n<pre class=\"scroll-box\"><code>\n[sudo] password for johndoe: \nMatching Defaults entries for johndoe on localhost:\n    !visiblepw, always_set_home, match_group_by_gid, always_query_group_plugin, env_reset, env_keep=\"COLORS DISPLAY HOSTNAME HISTSIZE KDEDIR LS_COLORS\", env_keep+=\"MAIL\n    PS1 PS2 QTDIR USERNAME LANG LC_ADDRESS LC_CTYPE\", env_keep+=\"LC_COLLATE LC_IDENTIFICATION LC_MEASUREMENT LC_MESSAGES\", env_keep+=\"LC_MONETARY LC_NAME LC_NUMERIC\n    LC_PAPER LC_TELEPHONE\", env_keep+=\"LC_TIME LC_ALL LANGUAGE LINGUAS _XKB_CHARSET XAUTHORITY\", secure_path=\/sbin\\:\/bin\\:\/usr\/sbin\\:\/usr\/bin, !visiblepw, always_set_home,\n    match_group_by_gid, always_query_group_plugin, env_reset, env_keep=\"COLORS DISPLAY HOSTNAME HISTSIZE KDEDIR LS_COLORS\", env_keep+=\"MAIL PS1 PS2 QTDIR USERNAME LANG\n    LC_ADDRESS LC_CTYPE\", env_keep+=\"LC_COLLATE LC_IDENTIFICATION LC_MEASUREMENT LC_MESSAGES\", env_keep+=\"LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER LC_TELEPHONE\",\n    env_keep+=\"LC_TIME LC_ALL LANGUAGE LINGUAS _XKB_CHARSET XAUTHORITY\", env_keep+=SSH_AUTH_SOCK, secure_path=\/sbin\\:\/bin\\:\/usr\/sbin\\:\/usr\/bin\n\nUser johndoe may run the following commands on localhost:\n    (ALL) ALL\n<\/code><\/pre>\n\n\n\n<p>If you have any thought about this guide, don\u2019t hesitate to drop in comments section.<\/p>\n\n\n\n<p>Other tutorials;<\/p>\n\n\n\n<p><a rel=\"noreferrer noopener\" href=\"https:\/\/kifarunix.com\/configure-sssd-for-openldap-authentication-on-centos-8\/\" target=\"_blank\">Configure SSSD for OpenLDAP Authentication on CentOS 8<\/a><\/p>\n\n\n\n<p><a rel=\"noreferrer noopener\" href=\"https:\/\/kifarunix.com\/how-to-create-openldap-member-groups\/\" target=\"_blank\">How to Create OpenLDAP Member Groups<\/a><\/p>\n\n\n\n<p><a rel=\"noreferrer noopener\" href=\"https:\/\/kifarunix.com\/configure-sssd-for-openldap-client-authentication-on-debian-10-9\/\" target=\"_blank\">Configure SSSD for OpenLDAP Client Authentication on Debian 10\/9<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>In this guide, we are going to demonstrate how to configure SSSD for LDAP Authentication on Rocky Linux 8. In our previous guides, we have<\/p>\n","protected":false},"author":3,"featured_media":9221,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rank_math_lock_modified_date":false,"footnotes":""},"categories":[1099,285,121],"tags":[248,286,1422,3587,3722,1131,3721],"class_list":["post-9213","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-openldap","category-directory-server","category-howtos","tag-ldap","tag-openldap","tag-openldap-sssd","tag-rocky-linux-8","tag-rocky-linux-openldap-authentication","tag-sssd","tag-sssd-on-rocky-linux","generate-columns","tablet-grid-50","mobile-grid-100","grid-parent","grid-50","resize-featured-image"],"_links":{"self":[{"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/posts\/9213"}],"collection":[{"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/comments?post=9213"}],"version-history":[{"count":4,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/posts\/9213\/revisions"}],"predecessor-version":[{"id":21777,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/posts\/9213\/revisions\/21777"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/media\/9221"}],"wp:attachment":[{"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/media?parent=9213"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/categories?post=9213"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/tags?post=9213"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}