This project contains anything related to the Auth application. This includes things like:
- Login
- Registration
- Multi-Factor Authentication (MFA)
- OAuth
This project contains anything related to the Auth application. This includes things like:
Looks good to me, thanks!
Fix typos reported by @aklapper.
Should be fine after these two changes :)
Thank you both for the conversation here and further thanks @Cigaryno for the patch! :)
Mention closed-source apps in addition to open-source apps per @aklapper
Per @aklapper, it's best to show both closed-source and open-source TOTP apps.
In T16018#21478, @Cigaryno wrote:In T16018#21476, @aklapper wrote:I'd personally not remove common proprietary software options (as it makes life of users potentially harder if they already have such an app installed) but list FOSS options first.
Some FoSS devs may not be familiar at all with open-source TOTP apps. I personally use Google Authenticator so I agree with you and also, I have my TOTP content on WinAuth too, which is unmaintained however I am not ready to switch TOTP app on my Windows PC (my revs from now on are created from an Ubuntu VM due to the arc troubles I am having on Windows).
In T16018#21476, @aklapper wrote:I'd personally not remove common proprietary software options (as it makes life of users potentially harder if they already have such an app installed) but list FOSS options first.
In D25934#25089, @aklapper wrote:I'd prefer not to remove common proprietary software options but list FOSS options first.
I'd personally not remove common proprietary software options (as it makes life of users potentially harder if they already have such an app installed) but list FOSS options first.
I'd prefer not to remove common proprietary software options but list FOSS options first.
I will submit a patch shortly.
I think you are right for unnecessary catetorization and sending notifications.
Cigaryno moved this task from Backlog to PHP 8.1 on the PHP 8 support board.
In T15848#19430, @valerio.bozzolan wrote:I would like to better understand the root problem.
Why changing the current user agent should improve the situation?
@valerio.bozzolan: thats not what Andre says. He says another area of the code uses a terrible user agent and we should change that to a better one at the same time.
I would like to better understand the root problem. I see that Cloudflare was showing a captcha to Phorge (what Phorge?). It seems it was because an user agent was missing. But aklapper said that we are already setting an user agent.
That would probably be a better User-Agent
/settings/panel/multifactor/ requires users to add a custom Name so there is likely code to adapt/reuse for /settings/panel/apitokens/
https://we.phorge.it/source/phorge/browse/master/src/applications/auth/adapter/PhutilGitHubAuthAdapter.php$57-58 uses a boring
$future->addHeader('User-Agent', __CLASS__); for this.
Thanks again :) Giving right credits
done...
Yeah, probably. I'll try to do it tonight.
Can this (I mean rPb445e1d80df9 )be backported into stable?