Changes to login to Wordpress sites

[Ben Cooksley]

On Tue, Aug 9, 2022 at 12:48 AM Scott Petrovic <scottpetrovic at gmail.com>
wrote:

> hi Ben,
>

HI Scott,


>
> Thanks for getting that set up. I tested out both the Matomo site and the
> WordPress krita.org and the "log in with OpenID" path works for me.
>
> Going forward, I guess we should try to do all our website logins with
> this? Is there any page or documentation on how to get this going if we
> decide to make a website in the future that needs this? I haven't done it
> before, so not sure how technical it gets setting it up. I imagine it is
> easier if you use a popular framework like WordPress or Drupal, but what if
> we do something with a static site generator or something else that doesn't
> have an easy plugin to set up?
>

This is standard OpenID Connect (an extension to the OAuth2 specification)
so anything that supports that flow should support login via KDE Invent
(Gitlab).
Going forward all contributor focused sites should use this yes.

Sites intended for users should supply their own login system.

Not sure why a static site would need a login though.

Cheers,
Ben


>
>
>
>
>
>
> On Mon, Aug 8, 2022 at 5:38 AM Ben Cooksley <bcooksley at kde.org> wrote:
>
>> Hi all,
>>
>> Continuing in the theme of migration of websites to using KDE Invent for
>> login, this evening I migrated all 7 of our Wordpress sites to use KDE
>> Invent login.
>>
>> You'll now find a "Login with OpenID Connect" link at the top of the
>> login page on all of those sites.
>>
>> If you are an existing user of those sites, it would be appreciated if
>> you could please try to login with the new method and confirm that all is
>> working well.
>>
>> Much like with stats.kde.org, i'll be removing the connection to
>> Identity from these sites once it has been confirmed that everything works
>> correctly.
>>
>> Next up will be our Drupal sites - which given the activity on some of
>> them may prompt a request to archive / redirect some of them elsewhere.
>> Each of those requests will be given it's own email.
>>
>> Many thanks,
>> Ben
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-community/attachments/20220809/5dd536f2/attachment-0001.htm>