{"id":1152,"date":"2008-09-17T23:12:18","date_gmt":"2008-09-17T21:12:18","guid":{"rendered":"http:\/\/notizblog.org\/?p=1152"},"modified":"2020-05-05T11:59:07","modified_gmt":"2020-05-05T09:59:07","slug":"wordpress-wird-openid-provider","status":"publish","type":"post","link":"https:\/\/notiz.blog\/2008\/09\/17\/wordpress-wird-openid-provider\/","title":{"rendered":"WordPress wird OpenID-Provider"},"content":{"rendered":"\n

Will Norris hat vorgestern ausf\u00fchrlich \u00fcber die neuen Features seines WordPress-Plugins berichtet. Das wohl interessanteste Feature von wp-openid 3.0 ist der neue OpenID-Provider<\/a>:<\/p>\n\n\n\n

\n\t

The next major release of wp-openid includes a built-in OpenID provider and delegation engine. This will certainly be the most exciting feature of this release for most people, so let me explain a bit how it works. Each authorized user on the WordPress blog will have an OpenID at the author posts URL (ie. http:\/\/example.com\/author\/admin). Authorization to use the OpenID provider is controlled based on user roles and is managed in the main OpenID settings page.<\/p>\n<\/blockquote>\n\n\n\n

Das Plugin kann in zwei verschiedenen Modi betrieben werden. Multi-user<\/em> erstellt aus jeder Autor-URL (z.B. http:\/\/example.com\/author\/admin\/) eine OpenID w\u00e4hrend blog-owner<\/em> f\u00fcr Private-Blogs mit nur einem Autor gedacht ist und die Home-URL zur OpenID (z.B. http:\/\/example.com) macht:<\/p>\n\n\n\n

\n\t

In multi-user, the default configuration, the server supports a feature in OpenID 2.0 called OpenID Provider driven identifier selection. What this means is that ANY user on that blog can enter the home URL as their OpenID, and the OpenID provider itself will make sure that the correct identifier is returned to the relying party. The final identifier will still be something like http:\/\/example.com\/author\/admin\/, but the user only needs to enter example.com at a relying party. If you\u2019ve used ever used Yahoo\u2019s OpenID provider, then you\u2019ve probably seen how this works.<\/p>\n<\/blockquote>\n\n\n\n

Zwei weitere spannende Features sind die Hooks, als Schnittstelle f\u00fcr z.B. andere Plugins…<\/p>\n\n\n\n

\n\t

I haven\u2019t sat down to document them all yet, but I\u2019m adding in more hooks for other plugins to add functionality. Want to pull profile data from FOAF instead of sreg? No problem, now you have a hook you can implement. This makes everything in the plugin much more lightweight and \u201cloosely joined\u201d which is always good. All of the existing non-core OpenID functionality (like SREG) is currently using these hooks.<\/p>\n<\/blockquote>\n\n\n\n

…und die Unterst\u00fctzung des OpenID-Firefox-Plugins (welches \u00fcbrigens auch mit der Version 2.x funktioniert) \u00fcber das DiSo XRDS-Simple Plugin<\/a><\/em>.<\/p>\n\n\n\n

Ich habe das Plugin bisher nur einmal ausprobiert, da es noch einige kleine Fehler hat und die Admin-Oberfl\u00e4che des OpenID-Providers noch g\u00e4nzlich fehlt. Trotz dieser kleinen Fehler merkt man, dass sich Will Norris f\u00fcr diese Version sehr viel Zeit (die er sicherlich auch hatte<\/a>) genommen hat und ich bin sehr gespannt auf die fertige Version.<\/p>\n\n\n\n

Wer sich nochmal ausf\u00fchrlich mit den Features besch\u00e4ftigen will, sollte unbedingt Will Norris‘ Artikel dar\u00fcber lesen:<\/p>\n\n\n\n