Token endpoint error

Personal Demographics Service (PDS) Personal Demographics Service FHIR API
21

Hi John,
I think we got there. Your help has been invaluable. Thanks very much.
this is a path for us to complete GP Connect.
I do believe our immediate next step are to submit this phase for the team to verify, then build the PDS Fihr API, first, do you agree with me, second can you please give us the right link to help us implement the PDS API?

22

John,
Can you please point us to any specific documentation on ‘passing the prompt parameter in as part of the call to the authorisation endpoint i.e. prompt=login?’

Regards

23

Hi John,
just had a feedback from developer, upon adding login prompt, it goes through hello, but after hello, it comes back to the authentication page below, how can we handle that?

----CIS2 Authentication

24

Please see the documentation for PDS FHIR API here: Personal Demographics Service - FHIR API - NHS England Digital

25

Thank you for sending this link.

26

@john.lister3 any guidance you can give us on the below please?

27

Hi Andre, I’m not sure what you are asking for or the issue. If you use prompt=login every call to the authorise endpoint will require authentication as designed:

just had a feedback from developer, upon adding login prompt, it goes through hello, but after hello, it comes back to the authentication page below, how can we handle that?

I would need more information as TBH this doesn’t make a lot of sense. What is hello? What is the flow, etc Feel free to DM me a HAR file for the flow from the browser debugger network tab.

28

by hello, I was referring to Windows hello as per the image below, it clears the authentication then returns to the authentication when the prompts are added. I will get the information from the developer and send to you shortly.

image
image1283×924 51.4 KB

29

Hi John,
please see the HAR file on this link please, it seems to be authenticating twice with the changes we made after your comments, but it looks like working now:

30

Why are you redirecting to this URL (see below) from your application and not our “authorize” endpoint as per the well known configuration?

https://am.nhsint.auth-ptl.cis2.spineservices.nhs.uk:443/openam/XUI/?realm=/nhsidentity/healthcare&goto=.....

correct url is
https://am.nhsidentity.spineservices.nhs.uk/openam/oauth2/realms/root/realms/NHSIdentity/realms/Healthcare/authorize

I’ve got to ask Andre if any of your development team have read our guidance pages as it doesn’t appear to be the case.

31

John,
we appreciate your help. They do read or may have missed. We will revert back.
Regards
Andre

32

Hi John
is this what is expected after the change?

33

Hi Andre, the initial URL you are using is still wrong - please refer to the developer guidance. The team appear to be guessing URLs

34

[quote=“john.lister3, post:33, topic:11304”]
Hi John,
please see the new HAR file after some changes have been made. Hopefully it’s in a state for you to point more or less exactly where we need to fix. Thanks in advance.