on 11-07-2017 8:52 AM
Hello Experts,
We participated @TechEd 2017 sessions, we are trying to achieve MDK(aka App Modeler) sample application by consuming sample mobile services.
Here we are facing issue with SEAM client generation.
After client generation ->start button – > login page couldn’t load with our cloud platform trail account settings.
We have done proper settings in BrandedSettings.JSON file configuration.
Please find below screenshot for your reference.
We have setup below things in BrandedSettings.json file
APP ID
Client ID
Server URL
Redirect URL
Authorization URL
Token URL
But with same settings for TechEd user it was working fine.
We have cross verified with modified URL and everything is same but still it didn’t work for our cloud platform Trail account.
Do we need any other authorization to achieve this or Is there any way to achieve with our trail account?
We have used different versions of SDK such as SAP Mobile SDK for iOS 2.0 Beta version, 1.9 version and initial version to build SEAM client.
Kindly suggest here to resolve this issue.
jitendrakumar.kansal martingrasshoff bill.froelich team any help or suggestion on above issue?
Thanks in advacne,
Jana
e.janarthanan
Quick guess, add comma (,) at the end of TokenUrl
Regards,
JK
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Jittu,
Thanks for your quick response, yea we actually added comma(,) at the end of TokenUrl, but still issue is remain same.. When we tried with SapTechEd user settings it works fine. just would like to know is there any limitation to access OAuth authentication at application security level for trail account.?
any solutions on above issue.?
For TechEd exercise, client was built by team already. Were you able to build client your own? No limitation to access OAuth as such
Well,
we have made MDK client available yesterday, download it.
Follow instruction README_SDK_Installer.md after unzipping it. (Xcode 9 required)
Let me know in case of any further hiccups.
Regards,
JK
You should really log a new question for this as it is a different issue than the original question.
You are missing a comma at the end of the TokenURL line in your BrandedSettings.json. The new v2 Mobile development kit that was just released this week (on the SAP Store) corrects this for the default BrandedSettings.json file.
When launching the client if you see Safe Default Data on the Welcome screen you know there is some problem with your BrandedSettings.
--Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.