search for: auth_request_set_field

In 1.2.1 there's: passdb-pam.c:230 status = pam_get_item(pamh, PAM_USER, &item); passdb-pam.c:237 auth_request_set_field(request, "user", item, NULL); so "item" is PAM_USER, which is then checked by auth_request_set_field: 1022 if (strcmp(request->user, value) != 0) { 1023 auth_request_log_debug(request, "auth", 1024...

...} + auth_request_log_warning(auth_request,AUTH_SUBSYS_DB, + "Multiple values found for '%s', " + "using combined value '%s'", name, values[0]); + auth_request_set_field(auth_request, name, values[0], + conn->set.default_pass_scheme); + } else { if (values[1] != NULL) { auth_request_log_warning(auth_request, AUTH_SUBSYS_DB, "Multiple values...

Hm, so my mailing list archive is up, but when I add nopassword to the list of settings in my passdb passwd-file I get: file auth-request.c: line 924 (auth_request_set_field): assertion failed: (request->passdb_password == NULL) Raw backtrace: dovecot-auth [0x806be11] -> dovecot-auth [0x806bd8c] -> dovecot-auth(auth_request_set_field+0x277) [0x80547d7] -> dovecot-auth [0x8060418] -> dovecot-auth [0x8060509] -> dovecot-auth(auth_request_verify_plain+0x...

I'm trying to hack together a new authentication back-end and I wanted to know if it's possible to pass values from passdb to userdb in the auth_request structure at authentication time. I modified struct auth_request in auth-request.h to contain a new variable and it gets set properly in my passdb, however the value is not there when checking for it userdb. I'm very novice when it

...p=<hidden> dovecot: auth-worker(default): sql(webmaster at example.com,0.0.0.0): query: SELECT username as user, NULL as password FROM users WHERE username = 'webmaster at example.com' AND password = PASSWORD('mypassword') dovecot: auth(default): file auth-request.c: line 723 (auth_request_set_field): assertion failed: (*name != '\0') dovecot: child 8552 (auth) killed with signal 6 My SQL conf: password_query = SELECT username as user, NULL as password FROM users WHERE username = '%u' AND password = PASSWORD('%w') as advised in a previous discussion in this list R...

...free(resp); + str_free(&username); return PAM_CONV_ERR; } resp[i].resp_retcode = PAM_SUCCESS; resp[i].resp = string; } + str_free(&username); *resp_r = resp; return PAM_SUCCESS; @@ -231,7 +241,10 @@ pam_strerror(pamh, status)); return status; } - auth_request_set_field(request, "user", item, NULL); + if (module->pam_allow_transform) + { + auth_request_set_field(request, "user", item, NULL); + } return PAM_SUCCESS; } @@ -257,6 +270,11 @@ struct pam_conv conv; enum passdb_result result; int status, status2; + const struct var_expa...

...get_item(pamh, PAM_USER, (linux_const void **)&item); if (status != PAM_SUCCESS) { *error = t_strdup_printf("pam_get_item() failed: %s", pam_strerror(pamh, status)); return status; } auth_request_set_field(request, "user", item, NULL); however it appeared to me that the auth process was passing this username to the parent in its response. Is this issue resolved? I compiled and tested mapping the username sso to the user andrew: Jun 27 13:38:45 itsrv dovecot: auth-worker(default)...

...db-blocking.c 2010-04-08 09:59:12.000000000 -0500 @@ -19,7 +19,8 @@ if (*args != NULL) { i_assert(auth_stream_is_empty(request->extra_fields) || - request->master_user != NULL); + request->master_user != NULL || + request->submit_user != NULL); /* APPLE - urlauth */ auth_request_set_fields(request, args, NULL); } } @@ -73,7 +74,8 @@ struct auth_stream_reply *reply; i_assert(auth_stream_is_empty(request->extra_fields) || - request->master_user != NULL); + request->master_user != NULL || + request->submit_user != NULL); /* APPLE - urlauth */ reply = aut...