[#38240] - [4] remove api-basic-auth-plg
- Closed
- 26 Nov 2022
- Medium
- Build: 4.2-dev
- # 38240
- Diff
- alikon:patch-4
User tests: Successful: Unsuccessful:
Summary of Changes
as per https://docs.joomla.org/Joomla_Api_Specification#Authentication
There is also a legacy basic authentication plugin for simple local development however this is likely to be removed before the release of Joomla 4.0.0 stable.
Testing Instructions
code review
Actual result BEFORE applying this Pull Request
there is still a basic authentication plugin
Expected result AFTER applying this Pull Request
no more basic authentication plugin
Documentation Changes Required
?
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | SQL Installation Postgresql Front End Plugins |
Besides that I think we can't do that with a minor version as it's a b/c break.
it should have been removed before 4.0 stable, how it can be a b\c break ?
because it wasnt removed and people could be using it
In j3 we still have the GMail plugin which is totally broken. So I think we should not remove extension in a minor version as we didn't do it in the past. It would be too disrupting.
@richard67 I don't think so that removing extensions is covered by our BC policy.
if really there is someone that even use it in the wild, which i strongly doubt, even then, they must be use the token one, just for security reason
"errare humanum est perseverare autem diabolicum"
@richard67 I don't think so that removing extensions is covered by our BC policy.
@laoneo I know that removing core extensions is not covered by our b/c promise. But having them as option in an API maybe is.
| Status | Pending | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2022-11-26 10:46:20 |
| Closed_By | ⇒ | alikon | |
| Labels |
Added:
?
|
||
As it is now, the PR doesn't handle removal of the plugin on core updates.