Context i'm going to speaking is stated as in subject you can see that option in jazn-data.xml.
when it will useful you may ask.
Consider the Scenario your main application is fully bounded with help of ADFSecurity. your child application not having security,
if you are try to consume Taskflow from your child application to the main application. ADFSecurity wont allow unauthorized Taskflow invocation.
we should make entry in jazn.xml to make it authorized. However you can't able to see your Child Application Taskflow even after imported.
At that time check the option you can able to see that child application taskflow.
To confirm the above statement. here i gave the snapshots.
Step 1: Secured Application(ADFSecuredApp).
Step 2: non - Secured Application(Genereal App).
Step 3: Make non-secured(GenerealApp) it as ADFLibrary. why mean i need the "general" task flow in secured application(ADFSecured App)
Step 4: you can see secured index page in ADFSecured Application
Step 5: Now in this ADFc-Config of Secured(ADFSecured Application) trying to invoke the non-Secured(Genereal Application). now if you run this page that taskflow never invoke.why because means not giving access to that bounded taskflow.
Step 6: Registering the Taskflow as Secured you can choose the Taskflow from drop down. but it is not avialable. even though you imported the non-secured(Genereal application).
Step 7: Now By checking the box you can able to see the imported Taskflow.
Step 8: Now Make it as authorized.
Step 9: After that Running the ADFSecured Application.
Step 10: you can see your index page.
Step 11: finally i can able to invoke the Genereal Application Taskflow in ADFSecured Application.
Download here
when it will useful you may ask.
Consider the Scenario your main application is fully bounded with help of ADFSecurity. your child application not having security,
if you are try to consume Taskflow from your child application to the main application. ADFSecurity wont allow unauthorized Taskflow invocation.
we should make entry in jazn.xml to make it authorized. However you can't able to see your Child Application Taskflow even after imported.
At that time check the option you can able to see that child application taskflow.
To confirm the above statement. here i gave the snapshots.
Step 1: Secured Application(ADFSecuredApp).
Step 2: non - Secured Application(Genereal App).
Step 3: Make non-secured(GenerealApp) it as ADFLibrary. why mean i need the "general" task flow in secured application(ADFSecured App)
Step 4: you can see secured index page in ADFSecured Application
Step 5: Now in this ADFc-Config of Secured(ADFSecured Application) trying to invoke the non-Secured(Genereal Application). now if you run this page that taskflow never invoke.why because means not giving access to that bounded taskflow.
Step 6: Registering the Taskflow as Secured you can choose the Taskflow from drop down. but it is not avialable. even though you imported the non-secured(Genereal application).
Step 7: Now By checking the box you can able to see the imported Taskflow.
Step 8: Now Make it as authorized.
Step 9: After that Running the ADFSecured Application.
Step 10: you can see your index page.
Step 11: finally i can able to invoke the Genereal Application Taskflow in ADFSecured Application.
Download here
No comments:
Post a Comment