| Age | Commit message (Collapse) | Author |
|
|
|
* Add analyzers to MediaBrowser.XbmcMetadata
* Enable TreatWarningsAsErrors for MediaBrowser.XbmcMetadata
* Add analyzers to MediaBrowser.WebDashboard
* Enable TreatWarningsAsErrors for MediaBrowser.WebDashboard
* Disable SA1600 in favor of CS1591
|
|
Allow changing capitalization of usernames
|
|
Co-Authored-By: Bond-009 <bond.009@outlook.com>
|
|
|
|
|
|
|
|
Delete user config dir on user deletion
|
|
|
|
Analyzers are only run in debug build, so setting TreatWarningsAsErrors
for release build will catch the compiler warnings until we resolve all
analyzer warnings.
|
|
|
|
Fix more warnings
|
|
Co-Authored-By: dkanada <dkanada@users.noreply.github.com>
|
|
|
|
* Make baseurl case-insensitive
|
|
Add clearer exceptions, warnings and docs
|
|
|
|
|
|
|
|
|
|
|
|
* Remove legacy auth code
* Adds tests so we don't break PasswordHash (again)
* Clean up interfaces
* Remove duplicate code
* Use auto properties
* static using
* Don't use 'this'
* Fix build
|
|
|
|
|
|
|
|
|
|
|
|
This reverts commit c230d49d7c37d4fbe77676b835c3afd6c8cb56e7.
This reenables an edge case where an admin might want to reset, with
the default auth provider, the password of an externally-provided
user so they could "unlock" the account while it was failing. There
might be minor security implications to this, but the malicious
actor would need FS access to do it (as they would with any password
resets) so it's probably best to keep it as-is.
Removing this in the first place was due to a misunderstanding
anyways so no harm.
|
|
This wasn't needed to prevent updating the policy on-disk from my
tests and can be removed as suggested by @Bond-009
|
|
|
|
Co-Authored-By: Claus Vium <cvium@users.noreply.github.com>
Co-Authored-By: Bond-009 <bond.009@outlook.com>
|
|
|
|
Implements the InvalidAuthProvider, which acts as a fallback if a
configured authentication provider, e.g. LDAP, is unavailable due
to a load failure or removal. Until the user or the authentication
plugin is corrected, this will cause users with the missing provider
to be locked out, while throwing errors in the logs about the issue.
Fixes #1445 part 2
|
|
|
|
The issue is that the new easyPassword format prepends the hash
function. This PR extract the hash from "$SHA1$_hash_".
|
|
|
|
Pass back the Username directive returned by an AuthenticationProvider
to the calling code, so we may override the user-provided Username
value if the authentication provider passes this back. Useful for
instance in an LDAP scenario where what the user types may not
necessarily be the "username" that is mapped in the system, e.g.
the user providing 'mail' while 'uid' is the "username" value.
Could also then be extensible to other authentication providers
as well, should they wish to do a similar thing.
|
|
Co-Authored-By: LogicalPhallacy <44458166+LogicalPhallacy@users.noreply.github.com>
|
|
|
|
Co-Authored-By: LogicalPhallacy <44458166+LogicalPhallacy@users.noreply.github.com>
|
|
|
|
|
|
|
|
Co-Authored-By: LogicalPhallacy <44458166+LogicalPhallacy@users.noreply.github.com>
|
|
|
|
|
|
|
|
|
|
|
|
|