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
I'm working on adding Single sign-on support for Cortex, similar to what is done in TheHive (TheHive-Project/TheHive#354). Currently this functionality is built in TheHive OAuth2Srv service.
Since this feature is now being added to Cortex, a similar service will have to be added there. Would it be better if the functionality from TheHive was split and added into elastic4play so both Cortex and TheHive can use the same service, thus avoiding code duplication?
I also ask this because there are plans to move away from ElasticSearch in the future and this might affect how elastic4play is being used.
The text was updated successfully, but these errors were encountered:
Request Type
Feature Request
Description
I'm working on adding Single sign-on support for Cortex, similar to what is done in TheHive (TheHive-Project/TheHive#354). Currently this functionality is built in TheHive OAuth2Srv service.
Since this feature is now being added to Cortex, a similar service will have to be added there. Would it be better if the functionality from TheHive was split and added into elastic4play so both Cortex and TheHive can use the same service, thus avoiding code duplication?
I also ask this because there are plans to move away from ElasticSearch in the future and this might affect how elastic4play is being used.
The text was updated successfully, but these errors were encountered: