My ideas

Have the cloud console also in the customer infrastructure in BYOI settings. Avoid "talking home"

currently this is far too small, we need to login every time

One of our consultants reported that the feature of showing the password in the Connection Wizzard when editing a connection represents a security issue for his client. He would like this feature to be disabled.

The Cloud console lets you add new access rules for IP filtering. Once created, rules can be edited or deleted, but they cannot be temporarily disabled. It would be useful to add a button to enable or disable a rule.

Sometimes it is necessary to see who changed the assigned license, but not it is not logged.

It is important to be able to extend the ability to synch models beyond just the current region (you cannot right now). Clients may want to have back up instances in different regions. I wanted to transferer a model from US to Germany Instance and...

In order to secure Jedox cloud console, i purpose to add an MFA to access to the cloud console. Actually, there is a simple Email/password but it's not enough securised.

A new (sample) svs script that drills not to the drillthrough dialog, but to an external website, with parameters passed from the intersection in the cube. When executing a drillthrough, a redirection to an external website like Salesforce should ...

This may refer to JS-I-1000. For security purposes I can deactivate the NOSSO url of Jedox Web in order to prevent any user to login without MFA. Meanwhile the OData API and the OLAP server browser can still be accessed without MFA. So I request a...

According to the knowledge-base and how things currently work, accessing the DB security (screenshot) within Jedox Cloud is only possible through either the built-in user "admin" or a user which is member of the built-in group "admin". Also access...