MindAccess Operator Plan Subscribers

Operator Cockpit

What's new?

  • Notification to operators in case of app status change to "remediation required". In this case a developer needs to provide a fixed application version as a vulnerability has been found.

  • Undeploy of Cloud Foundry apps: In the Operator Cockpit user interface you can now directly undeploy an application in your Cloud Foundry organization.

  • New application type "Fleet Manager PlugIn": The Operator Cockpit can now handle Fleet Manager PlugIns as a new application type.

User experience enhancements

  • In the wizard "Deployment" a new "Refresh" button provides more transparency on deployment status.

  • "Inbox" now represents a combination of "Application catalog" and "Notifications".

  • Improvements in content of: emails, messages, notifications and UI-labels.

Fixed issues

  • Deployment status: Status "Assigned" does not switch to "Deployed", even if the application was deployed in Cloud Foundry.

  • Deployment button is disabled after successful "cf push".

  • Registration of an application is sporadically not working.

  • Provisioning is sporadically not working.

  • Edit functionality for self hosted applications is not working consistently.

Known issues

  • Limitations for applications that use "Technical Token Manager API":

    • You cannot use zero downtime upgrade for applications that use "Technical Token Manager API", if the previous version of this application did not use "Technical Token Manager API".

  • Limitations for update of Clooud Foundry applications:

    • The service instance names for each service should be same in the current and new version of the application. If the service instance names are different in the new version and the existing version of an application, then the existing service instances will not be readily available even after zero-downtime version upgrade.

    • During manual deployment of a new version of an application, do not use the same component names as available in the existing version. This might create name conflicts and usability issues. In order to avoid such conflicts, while deploying a new version of an application, append green at the end of the component name.

  • For every individual (single) application, one Cloud Foundry space must be deployed.

  • After modifying the authorization of a user via the Operator Cockpit user interface, the change is not immediately visible. The user has to close the browser and login again.

  • After deployment of an app, there is a security feature in place validating if the app is known to MindSphere or the app has somehow been modified. Sometimes issues occur with regards to name changes or deploying from various folders. The apps need to be deployed as they are assigned from the developer.