NFR: Misc updates to imap authentication
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 45/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Estancado
- Stack tecnológico
- php
- Área
- authentication
Línea de trabajo
Start in lib/IMAP.php and review the constructor and authentication flow against the proposed addEmail and authSeparator settings. Verify the username, Nextcloud user ID, email, and domain-group behavior for each objective; completion requires addressing the three listed objectives, though no test file or IMAP test server is provided.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Objectives:
- avoid creation of accounts without the domain [Bug 128] (https://github.com/nextcloud/user_external/issues/128)
- add an email address to created users automatically
- allow a separator other than '@' during the actual IMAP authentication [Bug 150] (https://github.com/nextcloud/user_external/issues/150)
Summary:
Add two new config variables
- $addEmail (arg6) true: create email address matching login if login contains '@'
- $authSeparator (arg7) replace '@' with '$authSeparator' when authenticating to the IMAP server
(Note: I don't have any server to test this against...)
update lib/IMAP.php
Collect the new variables
diff -u IMAP.php apps/user_external/lib/IMAP.php
--- IMAP.php 2022-04-29 09:29:43.573148672 -0400
+++ apps/user_external/lib/IMAP.php 2022-04-29 09:41:59.878674898 -0400
@@ -25,6 +25,8 @@
private $domain;
private $stripeDomain;
private $groupDomain;
+ private $addEmail;
+ private $authSeparator;
/**
* Create new IMAP authentication provider
@@ -36,7 +38,7 @@
* @param boolean $stripeDomain (whether to stripe the domain part from the username or not)
* @param boolean $groupDomain (whether to add the usere to a group corresponding to the domain of the address)
*/
- public function __construct($mailbox, $port = null, $sslmode = null, $domain = null, $stripeDomain = true, $groupDomain = false) {
+ public function __construct($mailbox, $port = null, $sslmode = null, $domain = null, $stripeDomain = true, $groupDomain = false, $addEmail = false, $authSeparator = null) {
parent::__construct($mailbox);
$this->mailbox = $mailbox;
$this->port = $port === null ? 143 : $port;
@@ -44,6 +46,8 @@
$this->domain = $domain === null ? '' : $domain;
$this->stripeDomain = $stripeDomain;
$this->groupDomain = $groupDomain;
+ $this->addEmail = $addEmail;
+ $this->authSeparator = $authSeparator;
}
Look for the configured authSeparator in the login field and replace it with an '@' to be used for the NC username and email.
/**
@@ -61,12 +65,21 @@
$uid = str_replace("%40", "@", $uid);
}
+ $authseparator = strlen($this->authSeparator) == 1 ? $this->authSeparator : '@';
+
+ // Replace $authseparator with '@' in case the user used the wrong separator...
+ if (!(strpos($uid, '@') !== false) && (strpos($uid, $authseparator) !== false)) {
+ $uid = str_replace($authseparator, "@", $uid);
+ }
+
Set $useremail whenever we set $username. Use $authSeparator in $username for authentication to the IMAP server (addresses [Bug 150] (https://github.com/nextcloud/user_external/issues/150), but I have no server to test against )
$pieces = explode('@', $uid);
if ($this->domain !== '') {
if (count($pieces) === 1) {
- $username = $uid . '@' . $this->domain;
+ $username = $pieces[0] . $authseparator . $this->domain;
+ $useremail = $pieces[0] . '@' . $this->domain;
} elseif (count($pieces) === 2 && $pieces[1] === $this->domain) {
- $username = $uid;
+ $username = $pieces[0] . $authseparator . $pieces[1];
+ $useremail = $pieces[0] . '@' . $pieces[1];
if ($this->stripeDomain) {
$uid = $pieces[0];
}
@@ -79,8 +92,14 @@
}
} else {
$username = $uid;
+ $useremail = $uid;
}
Force the NC user id to match the full email (addresses Bug 128 )
-
+ if ($this->stripeDomain) {
+ $uid = $pieces[0];
+ } else {
+ $uid = $useremail;
+ }
+
$groups = [];
if ($this->groupDomain && $pieces[1]) {
$groups[] = $pieces[1];
Save the user's email in NC config if there's an '@' in it and $addEmail is true
@@ -104,6 +123,10 @@
curl_close($ch);
$uid = mb_strtolower($uid);
$this->storeUser($uid, $groups);
+ if ($this->addEmail && (strpos($useremail,'@') !== false) ) {
+ $config = \OC::$server->getConfig();
+ $config->setUserValue( $uid, 'settings', 'email', $useremail);
+ }
return $uid;
} else {
\OC::$server->getLogger()->error(
- Lenguaje dominante
- JavaScript
- Estrellas
- 121
- Forks
- 73
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de nextcloud/user_external
-
0. Needs triage bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
nextcloud/user_external#298 · 1 reacción ·
-
NC 35 compatibilityAbierto0. Needs triage enhancement
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
nextcloud/user_external#311 · 2 comentarios · 4 reacciones ·
-
0. Needs triage bug
Dificultad 3/5 1-2 días Aptitud para principiantes 68/100
nextcloud/user_external#310 · 2 comentarios ·
-
v4.0.0 released!Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 20/100
nextcloud/user_external#295 · 3 reacciones ·
-
0. Needs triage bug
Dificultad 3/5 1-2 días Aptitud para principiantes 52/100
nextcloud/user_external#281 · 6 comentarios · 3 reacciones ·
Todos los issues de nextcloud/user_external
Issues similares
-
Remove: Fox Deportes SDAbiertocheck:passed feeds:remove
Dificultad 1/5 Menos de una hora Aptitud para principiantes 65/100
iptv-org/database#37176 · 1 comentario · 1 reacción ·
Los mantenedores suelen responder en 9 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
hawk-digital-environments/HAWKI#443 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
Los mantenedores suelen responder en 1 día
-
feedback simulation workshop
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
githubnext/gh-aw-workshop#4370 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
AltimateAI/vscode-dbt-power-user#2089 ·