Ability to Manage SSO Users Directly in Cumulocity administration
We have users registered to our tenants using Single Sign-On (SSO). When selecting a user from the administration panel, a warning appears indicating that the user is managed by the identity provider. As a result, we are unable to disable or make ...
The Trusted Root Certificates should support the same Certificate on multiple tenants within an enterprise tenant
The Trusted Root Certificates should support the same Certificate on multiple tenants within an enterprise tenant. Itron supports many Trusted Root certificates and generates them as needed per manufacturing needs. What currently occurs is that if...
Support OAuth2 between micro services and core services
Support OAuth2 between micro services and core services Itron requires secure interaction between micro services and core services. This is mandated by our info Sec team. The request is to enhance the security between micro services and core servi...
Logs are Vanishing, after restart of Service (OOM)
https://getsupport.softwareag.com/servicedesk/customer/portal/2/SI-509929 In the suport ticket we were informed that it is default behvior of cumulocity that the logs of a microservice are lost as soon as it is restarted. If we have a problem with...
Regulatory bodies are asking for more data around security of medical devices. I have been recently informed (second hand) that the US regulatory body (FDA) may in the next year or two require a Software Bill of Materials for Medical Device IoT pl...
When we configured Cumulocity to integrate SSO with azure, we needed to use the custom template to have OAUTH2 work. Specifically, we needed to add the scope field and set the scope to ${clientId}/.default
moving up from child MO to parent MO in the hierarchy issue
Kemin encountered this situation: a Device has a child device assigned. An user has inventory read access on a device group, both devices are assigned to this device group. For Kemins use case, they need to find the ID of the parent device based o...
Frontend applications have the archive feature but it is not supported for microservice applications on our tenants and it makes it hard to switch between versions for microservices. Need rollback option, as for Applications.
Notification 2.0 - Each API need to have own Subscription Filter
Currently, Notification 2.0 Subscription Filters are not tied to the respective API. It's a common filter for API lists. Ideally, the same service is required to process Events, Alarms but filter conditions are different for each one.
Notification 2.0 Subscription Filters Allowing Custom Attribute Filter along with Type Filter
Some cases "Type Filter" is not good enough to filter events, alarms. It's better to give flexibility for user to allow configure custom attribute and it's filter conditions along with "Type"