Portal is still using old username after portal.conf update
search cancel

Portal is still using old username after portal.conf update

book

Article ID: 243767

calendar_today

Updated On:

Products

CA API Developer Portal

Issue/Introduction

We originally configured the 5.1 portal using a MySQL user called "s_user".  We then changed the MySQL user to a new one with the same privileges called "s_portal".

The old s_user user was disabled in MySQL. We configured this new user in the portal .conf (below). When starting the portal comes up completely, but we cannot login.

The logs in the authenticator container show that it's using the old username and not the new one.

We have removed all docker volumes in case it was stored there, but it still does the same.

 

-------- portal.conf --------

PORTAL_DOMAIN=host
PORTAL_ENROLL_NOTIFICATION_EMAIL=noreply@hostname
PORTAL_ENABLE_ANALYTICS=y
PORTAL_LICENSE_FILENAME=/opt/apim-portal-5.1-final/SSG_Enterprise_9.xml
PORTAL_DATABASE_TYPE=mysql
PORTAL_DATABASE_HOST=***.**.*.**
PORTAL_DATABASE_PORT=3306
PORTAL_DATABASE_USERNAME=s_portal
PORTAL_DATABASE_PASSWORD=*******

--------- Log errors in authenticator -----------

### Error querying database.  Cause: java.sql.SQLSyntaxErrorException: SELECT command denied to user 's_user'@'%' for column 'TENANT_ID' in table 'USER_ORG_ROLE'
### Cause: java.sql.SQLSyntaxErrorException: SELECT command denied to user 's_user'@'%' for column 'TENANT_ID' in table 'USER_ORG_ROLE'; bad SQL grammar []; nested exception is java.sql.SQLSyntaxErrorException: SELECT command denied to user 's_user'@'%' for column 'TENANT_ID' in table 'USER_ORG_ROLE

Environment

Release : 5.1

Component : API PORTAL

Resolution

Please make sure you remove the old user from all the functions, triggers etc. and replace it with the new user name