You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Login using the user defined in cortex_seed_initial_username
Expected behaviour
At this point I'd normally know what password to use, login and go on my merry way. However, this role currently defines 3 secrets none of which is working.
One secret is the API key, one is defined but unused (see #1) and the last secret doesn't work for login (i.e. cortex_crypto_secret.
Screenshots
The text was updated successfully, but these errors were encountered:
I must've been mistaken to think that Cortex holds enough information in ElasticSearch or configuration files to authenticate users.
Is the seeding logic based around the cortex_load_seed_data flag supposed to populate ElasticSearch with a pretend TheHive index containing the cortex_seed_initial_username and its password?
Describe the bug
The seed data loaded into ElasticSearch doesn't contain a password to authenticate to Cortex using the "initial username".
In my particular case I don't use LDAP or oAuth and I'd like a plain form login method.
To Reproduce
Using the following host variables:
cortex_seed_initial_username
Expected behaviour
At this point I'd normally know what password to use, login and go on my merry way. However, this role currently defines 3 secrets none of which is working.
One secret is the API key, one is defined but unused (see #1) and the last secret doesn't work for login (i.e.
cortex_crypto_secret
.Screenshots
The text was updated successfully, but these errors were encountered: