crust issueshttps://gitlab.daasi.de/CRUST/crust/-/issues2018-09-27T10:20:45+02:00https://gitlab.daasi.de/CRUST/crust/-/issues/57OIDC/Satosa integration2018-09-27T10:20:45+02:00Denis ArhOIDC/Satosa integration- [x] we need client id & secret for Crust
- [ ] refresh tokens?- [x] we need client id & secret for Crust
- [ ] refresh tokens?Version 1.0 (Alpha)Denis ArhDenis Arhhttps://gitlab.daasi.de/CRUST/crust/-/issues/82Improve activity log section2019-02-22T10:01:29+01:00Mia ArhImprove activity log sectionCurrently, we decided to hide the activity log section because it's very technical and we want to make it more user-friendly for an end non-tech-savvy users.
We need to discuss first what are the options.Currently, we decided to hide the activity log section because it's very technical and we want to make it more user-friendly for an end non-tech-savvy users.
We need to discuss first what are the options.Mia ArhMia Arhhttps://gitlab.daasi.de/CRUST/crust/-/issues/19Field Level Permissions in CRM2018-09-04T13:35:14+02:00Niall McCarthyField Level Permissions in CRMExample use case:
In many sales departments, staff are allowed to read one another's opportunities. However, they may not be allowed to edit other staff's opportunities or run reports on them. In other instances, it may be that the staf...Example use case:
In many sales departments, staff are allowed to read one another's opportunities. However, they may not be allowed to edit other staff's opportunities or run reports on them. In other instances, it may be that the staff member can only view their own opportunities.
The capability to set field level permissions in CRUST Microservice modules is essential.Tit PetricTit Petrichttps://gitlab.daasi.de/CRUST/crust/-/issues/5"Open" Application options in CRUST Tabs2018-09-12T17:16:05+02:00Niall McCarthy"Open" Application options in CRUST Tabs![Tab_Menu_0.1](/uploads/97f1372ad78cf6f21019a5147a12e356/Tab_Menu_0.1.jpg)
The approach we have is nice, but the main problem is that it lacks detailed options for users. Not all users will want to open an application in a CRUST Tab/Pa...![Tab_Menu_0.1](/uploads/97f1372ad78cf6f21019a5147a12e356/Tab_Menu_0.1.jpg)
The approach we have is nice, but the main problem is that it lacks detailed options for users. Not all users will want to open an application in a CRUST Tab/Panel. CRUST is an IAM system and it's important we don't turn it into UX prison. We should be able to offer an option to open externally to CRUST as well:
a) In local browser
b) On local desktop application. Clearly for desktop applications, we will support very few out of the box for our first version.
c) On local mobile application. Same as for desktop.
d) In some cases it may not be possible to open an application in CRUST. The admin console should be configurable to only present the viable "open" options in the tab menu.Juan MasuellesJuan Masuelles