to ensure that timer is started before initializing websockets. This was leading to instances where the websocket thought that the session
hadn't been started yet. Also fixed an issue where the session wasn't tearing down the $interval when AUTH_TOKEN_PER_USER had been exceeded.
Originally we were looking at the underlying project/inventory update
but we are now populating the name of project updates and inventory
updates a lot better so we'll just take their names
This moves the get-choices and get-labels services to the rest module
The get-choices service is also revamped so that a field name can be passed to check the options request json
All uses of get choices were revamped to utilize the new naming convention
* release_2.4.0: (94 commits)
Fix up location of apt key for mongo
Handle playbook_on_include events from v2 ansible
if basic auth in headers, don't use cookie token
Add a docker-ui container to the compose workflow
Fix custom inventory scripts on org deletion
adding check for missing session time from local storage
Properly handle idle/expired session across tabs
fixed system tracking date issues
Improve postgres user creation
Remove silly user check in postgres config
Fix typo in `clean` target
fixed sources scope regions issue
fixed scan date being the earlier one when identical
fixed the console errors for the sources scope
fixed console error
fixed standard out load for adhoc commands
fixing custom inventory script error
Revert "change list separator for adhoc host patterns"
Revert "update awFeature ldap to enterprise_auth"
Revert "Change delimiter from ':' to ','."
...
Slight tweak to the rbac for projects related to the user who created
them. IF a user created a project but it is orphaned/not associated
with an organization then they will be able to see/change it. If,
however, it is created and associated with an organization and then they
are removed as an org admin they will no longer have access to it.
Now, simply being the creator of a project does not convey any access
for users. You must be in a project/team that has access to it and you
must be an org admin for an org that has the project to be able to make
changes to it