Skip to Main Content
Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

Cumulocity IoT Platform Services

Showing 122

Software Bill of Materials

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...
Dave Presuhn 7 days ago in Cumulocity IoT Platform Services / Authentication & Authorisation 1 Already supported

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.
Venkatesu Punugupati 6 days ago in Cumulocity IoT Platform Services 0

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"
Venkatesu Punugupati 6 days ago in Cumulocity IoT Platform Services 1 Future consideration

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...
Andrew Nowak about 2 months ago in Cumulocity IoT Platform Services / Authentication & Authorisation 0 Future consideration

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...
Andrew Nowak about 2 months ago in Cumulocity IoT Platform Services 2 Clarification needed

disable unused features

Not all features are used by all users. For example, we do not use the platform to send commands to our medical devices. It would enhance security if features could be disabled so they could not be used by an attacker when they are not used as par...
Dave Presuhn 14 days ago in Cumulocity IoT Platform Services 0

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...
Guest 29 days ago in Cumulocity IoT Platform Services / Data at Rest 1 Planning / planned

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...
Guest about 1 year ago in Cumulocity IoT Platform Services / Product Infrastructure & Microservices 2 Work in progress

Archive Feature for Microservice Application

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.
oana velicu about 1 year ago in Cumulocity IoT Platform Services / Product Infrastructure & Microservices 2 Future consideration

Support User Functionality for Selected Tenants instead of All

In order to provide a service to a sub-tenant it is necessary to have authorization to the support user. However currently the support user cannot be limited to a specific set of sub-tenants,currently it is an all or nothing approach.
Venkatesu Punugupati about 2 months ago in Cumulocity IoT Platform Services / Platform Management 3 Future consideration