HelloI had a number of AuthZ workflows that would validate names such as SamAccount and group names against AD and then pass that information onto an action workflow. This seemed to work fine in RC0 but I'm having troubble with RC1. I'm using the ResourceProperties to store the infomation. The authorization workflow seems to correctly set the attribute, but when I then try to read it while executing the Action workflow it is not there. I can see that the workflow request has the same uuid so it is using the same request for both the authZ and action code. Has anybody run into this problem ? I suppose I could store the information in a file, thats kind of messy. My get and set code is listed bellow.Any ideas would be appreaciatedThanks public static string GetCurrentRequestProprtie(RequestType Request, string Attribute) { // System.Diagnostics.Debugger.Launch(); string Value=string.Empty; if (Request.ResourceProperties.ContainsKey(Attribute)) { Value = Request[Attribute].ToString(); } Utils.SimpleLogFunction("GetCurrentRequestProprtie", "GetCurrentRequestProperties", "Finding Current Request " + Attribute + " = " + Value, 202, 203); return Value; } public static void UpdateCurrentRequestProperties( RequestType Request, string Attribute, string Value) { if (!Request.ResourceProperties.ContainsKey(Attribute)) { Request.ResourceProperties.Add(Attribute, new ResourcePropertyInfo(Attribute, "stringtype", false, false)); } Request[Attribute] = Value; }

Hi Kevin, In order to pass data between an AuthZ Workflow and an Action Workflow for the same Request, you'll need to do the following:1. Create a new attribute in the FIM Schema. Eg. "RequestTempData"2. Bind the attribute to the Request object type in the schema.3. Grant permissions to the resource used as the ActorID in your AuthZ activity to update the new attribute. If you are using the "Forefront Identity Manager Service Account" Resource as the ActorID, then no such MPR is needed.4. In your AuthZ Workflow, use the UpdateResourceActivity to set the desired value on the new attribute.5. In your Action Workflow, use the ReadResourceActivity to read the value from the attribute.Hopefully this helps you accomplish your scenario.Thanks,Nima

ThanksI'll give it a try. I was under the impression that AuthZ workflows could not update attributes though, is that just a rights issue with the actorID ?