I was having an issue using my AD account to log into the BCC in the load test environment. In production, we have deleted the admin account for security reasons. This forces users to use their LDAP credentials, which is good.
In the short run, however, I needed to quickly login so I could troubleshoot an indexing issue.
I traced in the database during a failed login attempt, and found the following tables need to be populated with the values below.
insert into dpi_user (id,login,auto_login,password,member,first_name,user_type,
lastpwdupdate,generatedpwd,email_status,receive_email,gender)
values('portal-admin','admin',0,'n6CtgGHE4rfKqT/uObfXMQ==',1,'admin',0,sysdate,0,0,0,1);
insert into dpi_user_roles(USER_ID,ATG_ROLE) values('portal-admin','epubSuperAdmin');
insert into dpi_user_roles(USER_ID,ATG_ROLE) values('portal-admin','portal-admin');
insert into dpi_user_roles(USER_ID,ATG_ROLE) values('portal-admin','srchSearchAdminRole');
insert into dpi_user_org (ORGANIZATION,USER_ID) values ('root','portal-admin');
insert into dpi_user_org_anc(USER_ID,SEQUENCE_NUM,ANC_ORG) values ('portal-admin',0,'root');
commit;
Restart the BCC, and this will result in an admin/admin user you can use (in 10.0.3, anyway) to login to the BCC.