login
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
login [2012/12/17 09:10] richard |
login [2013/10/09 09:48] (current) |
||
|---|---|---|---|
| Line 13: | Line 13: | ||
| parameters: | parameters: | ||
| |auth | the authorisation code you received from Intogolf BV (mandatory)| | |auth | the authorisation code you received from Intogolf BV (mandatory)| | ||
| - | |pwd | client password (mandatory)| | + | |pwd | client password (mandatory) or authHash| |
| |relnr | client id| | |relnr | client id| | ||
| |email | email address| | |email | email address| | ||
| Line 26: | Line 26: | ||
| * name and pwd | * name and pwd | ||
| (warning: eventhough the securitylevel of these combinations will be very high, it is still no guarantee for a result set of 1 record only, because people may have double registrations with the same password) | (warning: eventhough the securitylevel of these combinations will be very high, it is still no guarantee for a result set of 1 record only, because people may have double registrations with the same password) | ||
| + | |||
| + | When you have an authHash value for a client you can supply the authHash value in the pwd field. In this case the relnr field is mandatory. You can retrieve the clients authHash by loggin in as described above or with [[addrelation|/igg/addrelation]]. | ||
| + | |||
| + | Please note that a relnr may become invalid at some point in time due to merging double accounts or deleting accounts. | ||
| Example: https://backend.ikgagolfen.nl/igg/login?auth=<your authrisation code here>&email=richard@intogolf.com&pwd=golf | Example: https://backend.ikgagolfen.nl/igg/login?auth=<your authrisation code here>&email=richard@intogolf.com&pwd=golf | ||
| Line 35: | Line 39: | ||
| "relnr": 602234, | "relnr": 602234, | ||
| "name": "R.J.W. Knol", | "name": "R.J.W. Knol", | ||
| + | "lastname": "Knol", | ||
| + | "nameprefix": "", | ||
| + | "initials": "R.J.W.", | ||
| + | "firstname": "Richard", | ||
| "mv": 2, | "mv": 2, | ||
| "email": "richard@intogolf.com", | "email": "richard@intogolf.com", | ||
| Line 44: | Line 52: | ||
| "privacy": 0, | "privacy": 0, | ||
| "securitylevel": 9, | "securitylevel": 9, | ||
| - | "relkey": "68de29c0547a5c23ad51f62154d1177c" | + | "relkey": "68de29c0547a5c23ad51f62154d1177c", |
| + | "authHash": "8c3a492b9bd0740d702a88c5776f8762" | ||
| } | } | ||
| ] | ] | ||
| Line 52: | Line 61: | ||
| |mv |the gender| | |mv |the gender| | ||
| |golferid |corresponds to the parameter “ngf”| | |golferid |corresponds to the parameter “ngf”| | ||
| - | |relkey |This hash key needs to be stored and is later on needed when you want to retrieve any personal data for the golfer| | + | |relkey |This hash key needs to be stored and is later on needed when you want to retrieve any personal data for the golfer. Beware that the combination relnr and relkey will not be valid forever. A user account can be deleted or merged to prevent doubles, in which case the relnr and relkey will become invalid. If you use an invalid relkey or a valid relkey in combination with a deleted relnr 401: Unauthorized will be returned when you try to use the relnr + relkey ombination in one of the other API functions| |
| |privacy |if 1, the user has checked a box indicating that he does not want his name to appear in search lists on other user’s sessions. For instance: you can not select them as co player unless they are in your friends lists. You can not add them to your friends list either, because they are not visible when you search for them. Your application will need to respect this. People with privacy set to 1 wil only appear in your result list if the securitylevel is at least 8, which means that he logged in with his password.| | |privacy |if 1, the user has checked a box indicating that he does not want his name to appear in search lists on other user’s sessions. For instance: you can not select them as co player unless they are in your friends lists. You can not add them to your friends list either, because they are not visible when you search for them. Your application will need to respect this. People with privacy set to 1 wil only appear in your result list if the securitylevel is at least 8, which means that he logged in with his password.| | ||
| |sid |if getoldstylesessionid=1 you will receive a session id to pass to the old style ikgagolfen iframes as &sid=<sessionid>&q=<checksum>| | |sid |if getoldstylesessionid=1 you will receive a session id to pass to the old style ikgagolfen iframes as &sid=<sessionid>&q=<checksum>| | ||
| Line 58: | Line 67: | ||
| If a wrong authorisation code is provided, the backend will return “no authorisation” | If a wrong authorisation code is provided, the backend will return “no authorisation” | ||
| - | |||
login.1355735401.txt.gz · Last modified: 2012/12/17 09:10 (external edit)
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
