[OPENIDM-15272] Note restriction on relationship configuration with a DS repo Created: 06/Aug/20  Updated: 12/Aug/20  Resolved: 12/Aug/20

Status: Closed
Project: OpenIDM
Component/s: documentation
Affects Version/s: 7.0.0
Fix Version/s: 7.0.0

Type: Bug Priority: Major
Reporter: Lana Frost Assignee: Lana Frost
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Target Version/s:
Verified Version/s:
QA Assignee: Son Nguyen
Story Points: 0.5
Sprint: 2020.10 - IDM

 Description   

When you define relationships between objects with a DS repo, the relationships need to be defined in managed.json and in the repo config (repo.ds.json). This is not the case when you define a relationship in the Admin UI.

This PR allows you to return the relationships for a DS repo, but unless you define the relationship in the repo config, there will be no filtering or sorting for a query like openidm/managed/user/<_id>/managedOrgs?_pageSize=50&_sortKeys=_id&_totalPagedResultsPolicy=ESTIMATE&_queryFilter=true&_fields= and no privilege filtering on relationship fields in a request like managed/user/<_id>?_fields=managedOrgs/*.

So, unless you define the relationship in the repo config, you won't be able to filter or sort relationship queries (including delegated admin privilege filters).



 Comments   
Comment by Lana Frost [ 07/Aug/20 ]

https://stash.forgerock.org/projects/OPENIDM/repos/openidm-docs/pull-requests/2913/overview
https://ea.forgerock.com/docs/idm/objects-guide/explicit-generic-mapping.html#relationship-properties-ds

Comment by Son Nguyen [ 10/Aug/20 ]

In https://ea.forgerock.com/docs/idm/release-notes/deprecated-functionality.html > oauthReturn Endpoint I don't see the IDM version, it shows "IDM ${platform-vers.ext}" instead

Comment by Lana Frost [ 12/Aug/20 ]

https://stash.forgerock.org/projects/OPENIDM/repos/openidm-docs/pull-requests/2919/overview

Comment by Son Nguyen [ 12/Aug/20 ]

Verified successfully on master

Generated at Tue Nov 24 20:44:51 UTC 2020 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.