Confluence 7.12.2 authentication plugin fails due to schema issue

[europoint]

Running 7.12.2 in the standard docker container, and I am unable to log in because an error occurs stating that a particular table in the confluence database doesn't exist.

The table does exist, but in the bitbucket schema.

There is no Confluence documentation that suggests how you can force Confluence to just look at the confluence schema and not any other schemas running on the database instance - the documentation just says "don't use the same schema".

So

1. How do I force Confluence just to look at it's own schema (parameters in server.xml or confluence.cfg.xml?

2. Why can't Atlassian list the parameters in confluence.cfg.xml, because it never used to be a requirement for this value to be forced?

3. Why can't Atlassian make sure their code actually checks the schema it should be using? The error actually says "Table 'confluencedb.AO_ED669C_IDP_CONFIG' doesn't exist" yet, it's obviously enumerating tables without checking the schema in the first place!

[Matt]

Any luck with this? We're currently running into it now in 7.11.2. Funny thing is that it's happening in our non-prod environments while prod shows no sign of the issue (for now that is...)

[europoint]

Apologies for the extremely late reply - I didn't get any email notifications of a response. It's likely that you have resolved this, but if anyone else is having a similar issue, please check the confluence.cfg.xml file for the following property:

<property name="hibernate.default_schema">{dbname}</property>

If not, add it, replacing {dbname} with the name of your Confluence database.

Restart Confluence. I think that resolves the issue (it's been a while!)