-
Type:
Suggestion
-
Resolution: Low Engagement
-
None
-
Component/s: None
-
Environment:
System Information
Date:
Tuesday, 15 Sep 2009
Time:
01:23:28
Timezone:
Central Standard Time
Java Version:
1.6.0_13
Java Vendor:
Sun Microsystems Inc.
JVM Version:
11.3-b02
JVM Vendor:
Sun Microsystems Inc.
JVM Runtime:
Java HotSpot(TM) Server VM
Username:
SYSTEM
Operating System:
Windows 20035.2
Architecture:
x86
Crowd Information
Home Directory:
E:\crowd-home
JVM Statistics
Total Memory:
126 MB
Used Memory:
95 MB
Free Memory:
31 MB
Database Information
JDBC URL:
jdbc:mysql://localhost/crowd?autoReconnect=true&characterEncoding=latin1&useUnicode=true
JDBC Driver:
com.mysql.jdbc.Driver
JDBC Username:
crowduser
Hibernate Dialect:
org.hibernate.dialect.MySQL5InnoDBDialect
Runtime Information
Application Server:
Apache Tomcat/5.5.25
Version:
1.6.1
Build Number:
391
Build Date:
Feb 17, 2009
License Information
License Server ID:
BU38-85YF-CEJ4-F7FDSystem Information Date: Tuesday, 15 Sep 2009 Time: 01:23:28 Timezone: Central Standard Time Java Version: 1.6.0_13 Java Vendor: Sun Microsystems Inc. JVM Version: 11.3-b02 JVM Vendor: Sun Microsystems Inc. JVM Runtime: Java HotSpot(TM) Server VM Username: SYSTEM Operating System: Windows 20035.2 Architecture: x86 Crowd Information Home Directory: E:\crowd-home JVM Statistics Total Memory: 126 MB Used Memory: 95 MB Free Memory: 31 MB Database Information JDBC URL: jdbc: mysql://localhost/crowd?autoReconnect=true&characterEncoding=latin1&useUnicode=true JDBC Driver: com.mysql.jdbc.Driver JDBC Username: crowduser Hibernate Dialect: org.hibernate.dialect.MySQL5InnoDBDialect Runtime Information Application Server: Apache Tomcat/5.5.25 Version: 1.6.1 Build Number: 391 Build Date: Feb 17, 2009 License Information License Server ID: BU38-85YF-CEJ4-F7FD
-
1
Allow the Administrator to define a required username format, i.e. first.last
The administrator should be able to force naming conventions to maintain standards. When users have the ability to create there own accounts (for crowd currently through jira), they do not know or follow standards.
Examples of solutions would be to automatically generate usernames from the full name field or from some (or all) of the email address field. Also an acceptable solution would be the ability to display the required format during the creation process.
