It's not 100% clear what your expectation is. We never display the user 'id' (which is a sequential number used only internally). Are you referring to the username (i.e. 'asterix67') ?

If that's the case, try setting

$g_show_realname = ON;
$g_show_user_realname_threshold = ANYBODY;

$g_use_ldap_realname only tells Mantis to always dynamically retrieve the name from LDAP instead of using the one stored in the DB (which, since it's normally copied from LDAP, acts like a cache) when displaying the Realname.

Hope this helps
Bonne journée

PS: as a side note, I recommend you upgrade to 1.2.19.

Thanks a lot dregad i try tomorrow.

Have a nice day too.
Bonne journée à toi ;-)

Hi,
It's ok the issue can be closed :
I had forgotten $g_ldap_realname_field = 'cn'

Thanks.

Just two questions or problems ...

In the LDAP of my company we have LDAP username > 30 characters.
How can i input the username in the username field of the "create new user" windows ? (The max of the field is 30 characters).

Another question : why realname and email fields are protected in my "create new user" windows ?

Thanks

Hi,

OK i understand my first problem: the column username in the mantis_user_table is in varchar2(32).

So i need to create manually a user with a username < 30 characters and with the same LDAP email of the LDAP user with username > 30 characters.

But it's impossible : the realname and email fields are protected in the "create new user" windows when i want create a new user.

Why ? i don't understand . Thanks for your help.

The only way is to insert the user in the database by a insert SQL command with mySQL ???

Another question : why realname and email fields are protected in my "create new user" windows ?

When $g_use_ldap_realname is ON, the master data is in LDAP, and Mantis fields are only used as cache, so it does not make sense to edit them because any changes would be overwritten sooner or later, usually with the user's next login.

With regards to username field size, this is a known issue, see 0008017. I can't think of any workaround except manually patching your system (modifying the DB_FIELD_SIZE_USERNAME constant and altering username column in DB, via SQL).
This may cause issues with future upgrades, so do this at your own risk.

OK super for example to increase to 64 characters max:

1) with SQL :
alter table mantis_user_table change username varchar(64);

2) /core/constant_inc.php :
define ( 'DB_FIELD_SIZE_USERNAME',64);

3) for the future installation database :
admin/schema.php :
$g_upgrade[196]=array( 'AlterColumnSQL', array( db_get_table( 'user '), "username C(64) $t_notnull DEFAULT \" '

Thanks a lot.

Do NOT alter schema.php, that will 100% cause issues with future upgrade. As I said before, alter the field by issuing an SQL DDL command to increase column size directly in your RDBMS.