I am working on implementation new Mobil SSO Project ( MAG 4.x & OTK 4.x) . I am looking out for some info. that could better explain the MAG Process backend and the to dos for on-boarding an application on to MAG and use MAG SDK.
1. ER Diagram for MAG and OTK Databases.
2. From the time of registering a device to removing the JWT ( logout), what all info gets populated in to DB tables and how to correlate them.
3. Details on OTK and MAG policies will be invoked when the request/flow happens.
Thanks in Advance.
What have you already looked at regarding the MAG process? This will help to understand what you have looked at so we can provide something that you haven't already seen.
Here is a product overview of MAG with explanations about how it works.
About MAG - CA Mobile API Gateway - 4.0 - CA Technologies Documentation
You can also see the CA MAS developer website for video tutorials, sample apps, code examples, and SDK API documentation - On this link there is a video tutorial that has steps for getting started with the Mobile SDK.
Thanks for the quick response. I went through the documentation but don't want to say the fullest.
Based on videos, we get the respective platform based sdk, add to the project assets and add the Json and run the sample app.
But some how not able to see the big picture on whats happening in back drops.
Policies acting in each scenario vs the data flow, unless they are some where in the api documentation.
I had a look for such resources and was unsuccessful. An engineer I spoke to suggested that, if you need to, raise a case with us where an engineer can go through this with you visually on a web-ex call. If not then hopefully someone else in the community can provide the answer you are looking for.
I don't know how relevant these may be to you (docs within CA API Gateway 9.2 and OTK 4.0) but I came across a few pages that talk about policies and they may be useful.
Developing a Policy
Composing Policy Logic