[00:29:46] <wm-bb>	 <gtisza> Should be fixed now. (re @Poslovitch: Hey there, I am getting some issues trying to upload a file to the Beta Cluster's Wikimedia Commons.
[00:29:46] <wm-bb>	 <gtisza> It keeps sending back this ...)
[16:28:53] <wm-bb>	 <Poslovitch> Actually, it's more like I forgot to update the provider URL. OAuth tokens validate that they were issued for the proper URL, which they weren't (cause, as I said, I messed up the provider URL on my side). Once having that fixed, it's working fine ;) (re @tuukkahastrup: Wow, what? This is interesting. To make sure I understand: You register an OAuth consumer application and it ge <clipped message>
[16:28:54] <wm-bb>	 <Poslovitch> ts rejected but y...)
[16:29:34] <wm-bb>	 <Poslovitch> Well, thank you! I'll move back to testing on the Beta Cluster then ;) (re @gtisza: Should be fixed now.)
[16:51:46] <wm-bb>	 <tuukkahastrup> It's confusing which approaches work and which don't - I suppose it's somewhat the nature of security-related functionalities such as OAuth. I think I've been using tokens from production deployment in the localhost deployment while developing, but now you're saying that doesn't (always?) work? (re @Poslovitch: Actually, it's more like I forgot to update the provider URL. OAuth t <clipped message>
[16:51:46] <wm-bb>	 <tuukkahastrup> okens validate that they were issued for the proper URL, wh...)
[18:52:48] <wm-bb>	 <Poslovitch> It doesn't work, if and only if you mess up the configuration. Having a consumer set up is easy, but if, on your end, you provide values that are invalid (invalid consumer secret, invalid provider URL), then the OAuth won't work, because it's designed to fail in such cases.
[21:03:18] <wm-bb>	 <gtisza> Tokens are bound to the wiki (or wiki farm) where they were generated. (re @tuukkahastrup: It's confusing which approaches work and which don't - I suppose it's somewhat the nature of security-related functionalities su...)