So, if you're defining a custom workflow, and you're adding your interface to the portal for the first time, you may get the error, "Create Resource: Access denied." Here's a screen shot:
So the fix is to define an MPR to allow you to create these guys. Note that there is already an MPR that allows Administrators to read all resources, so we'll avoid the redundancy here.
| Display Name | Administration: Administrators have full control over Activity Information Configuration resources |
|---|---|
| Action Parameter | * |
| Action Type | Add; Create; Delete; Modify; Remove |
| Action Workflows | 0 |
| Authentication Workflows | 0 |
| Authorization Workflows | 0 |
| Description | Administration: Administrators have full control over Activity Information Configuration resources |
| Grant Right | TRUE |
| Principal Set | Administrators |
| Resource Current Set | All Activity Information Configurations |
| Resource Final Set | All Activity Information Configurations |
Thank YOU!!!!!!!!!!!!!!!
ReplyDeleteDefinitely a useful post :)
ReplyDeleteSome of the missing MPR's that you'd expect by default are shocking!
This is actually not the correct solution.
ReplyDeleteThe reason you get this error is because there is a bug in FIM.
The built-in MPR called 'Administration: Administrators control configuration related resources' has a small typo in it.
Solution:
1.Open the MPR 'Administration: Administrators control configuration related resources'
2.Go to 'Advanced View'
3.Go to 'Extended Attributes'
4.In the 'Action Parameter' attribute change the wrongly spelled 'IsAuthoriztionActivity' to 'IsAuthorizationActivity'
5.Save the change.
That's what I call a useful post! You did it very good, without any unnecessary screens or information. I like the way you did it. I think I should browse your blog and maybe even put it to my rating of Rephraser.net as one of the best tech blogs. i hope you will help me even more later.
ReplyDeleteThis is helpful information to know, thanks for sharing.
ReplyDelete