Ah, never mind, I missed the OAuth section in the documentation! Will
request the new consumer then, thanks.

On Fri, May 15, 2020 at 3:53 PM Arthur Smith <[email protected]> wrote:

> Hi all - I was exploring my tool (author-disambiguator) - which uses
> OAuth. Is there a recommended practice for fixing/updating the OAuth
> details? I got an OAuth error when I first connected using the new URL, but
> that was I think because the callback is hardcoded in the OAuth
> configuration to the old server. Anyway, what are other people doing to fix
> this? Should I request new OAuth credentials for the new URL?
>
>    Arthur
>
> On Mon, May 4, 2020 at 11:59 AM Arturo Borrero Gonzalez <
> [email protected]> wrote:
>
>> Hi there!
>>
>> This is a reminder about the ongoing migration for the new domain and
>> URL/path
>> scheme for webservices running in Toolforge. On 2020-05-31 we have the
>> soft
>> deadline for this migration period.
>>
>> For trying the change you only need to run the webservice command with the
>> --canonical argument. Please review the documentation here:
>>
>> https://wikitech.wikimedia.org/wiki/News/Toolforge.org
>>
>> Early adopting this change is interesting for many reasons, specially a
>> more
>> secure environment by means of proper domain isolation. Also, the new
>> domain
>> better reflects the identity of the Toolforge service :-)
>> Moreover, during the compatibility period, we would like to collect
>> feedback and
>> bug reports from our users before the soft deadline.
>>
>> As of today, we have 40 tool webservices that are running in the new
>> domain and
>> using the new path scheme, find them here:
>>
>> https://replag.toolforge.org
>> https://testwikis.toolforge.org
>> https://meetingtimes.toolforge.org
>> https://speedpatrolling.toolforge.org
>> https://wiki-tennis.toolforge.org
>> https://xslack.toolforge.org
>> https://urbanecm-test-1.toolforge.org
>> https://wdmm.toolforge.org
>> https://quickcategories.toolforge.org
>> https://wikiportretdev.toolforge.org
>> https://zppixbot-test.toolforge.org
>> https://anticompositetools.toolforge.org
>> https://james.toolforge.org
>> https://bd808-ruby.toolforge.org
>> https://ytcleaner.toolforge.org
>> https://wd-shex-infer.toolforge.org
>> https://github-pr-closer.toolforge.org
>> https://wikistream.toolforge.org
>> https://secwatch.toolforge.org
>> https://giftbot.toolforge.org
>> https://pagepile-visual-filter.toolforge.org
>> https://zppixbot.toolforge.org
>> https://stashbot.toolforge.org
>> https://moedata.toolforge.org
>> https://sal.toolforge.org
>> https://covid-obit.toolforge.org
>> https://docker-registry.toolforge.org
>> https://wb2rdf.toolforge.org
>> https://massmailer.toolforge.org
>> https://wd-image-positions.toolforge.org
>> https://versions.toolforge.org
>> https://lexeme-forms.toolforge.org
>> https://ukbot.toolforge.org
>> https://machtsinn.toolforge.org
>> https://bikeshed.toolforge.org
>> https://gmt.toolforge.org
>> https://ipcheck.toolforge.org
>> https://signatures.toolforge.org
>> https://templatedata-filler.toolforge.org
>> https://wordcount.toolforge.org
>>
>> Please reach out for any comments, doubts or questions.
>>
>> regards.
>>
>> --
>> Arturo Borrero Gonzalez
>> SRE / Wikimedia Cloud Services
>> Wikimedia Foundation
>>
>> _______________________________________________
>> Wikimedia Cloud Services mailing list
>> [email protected] (formerly [email protected])
>> https://lists.wikimedia.org/mailman/listinfo/cloud
>
>
_______________________________________________
Wikimedia Cloud Services mailing list
[email protected] (formerly [email protected])
https://lists.wikimedia.org/mailman/listinfo/cloud

Reply via email to