I am confused by this response. I found the register() function in the php client documentation. It should be register($userid,$request);. For the $userid I am planning on using the email_address. For the $request I plan on using this:
$applicationId = "32688330-1630-4e0d-a4de-8ae45c3ca527";
$request = array();
$request["applicationId"] = $applicationId;
$request["loginId"] = $post_array[employee_email];
$request["password"] = "";
So it would be register($post_array[employee_email],$request);
Is this the proper API call to register a user? This is returning a $result->errorResponse of null.
What does this mean? Was the install bad?
This line seems to have executed correctly (I think)
$_SESSION['client'] = new FusionAuth\FusionAuthClient($apiKey, "http://localhost:9011");
I'm taking the first step in bringing a classic-ASP app into the 21st century, replacing the existing authentication with fusionauth.
Once I've added google as a social auth provider and a user attempts to login, the google authentication part happens (user is sent to google and logs in there), but then I'm just stuck on the screen below... never redirected to the redirect_uri or anything.
Hmmm. That's curious. Is there any information about the error in the event log or log tabs (under system)?
What version of FusionAuth are you running?
Also, i noticed if user clicks on create an account it goes to the registration page, which doesn't have a register with google link, even though I've enabled that "create registration" flag in the google settings for my application.
So if you enable "create registration" that means that a user can authenticate with google and then be automatically registered for the given FusionAuth application. This means they'll be authorized to access that application (and receive a 200 when authenticating against it).
Is FA the best place to have such time of queries or should I create a pipeline and publish updates elsewhere?
I think you have a couple of choices:
build a pipeline based on webhooks, possibly publishing each user to s3 or another datastore
querying elasticsearch directly
changing to the database engine
Given your other requirements (the ability to pick off just the phone number and name), I'd test out querying elasticsearch directly, or, if your queries are all simple, switching to the database search engine.
I'd pursue the pipeline approach only if the direct queries didn't perform well, because it's more moving pieces to break.
Is there an API planned which can allow me to get users data with specific fields - name, phone number or just the data field?
This is not currently planned, but feel free to open a feature request with more details. Feel free to reference this post and your previous github comment. I could see that being a useful API change, similar to how you can specify sort fields.
Is it advisable to modify elastic search to index only certain properties and get results directly from there without fetching the database - Bypassing FA APIs? (I have updated the index.max_result_window to the number of results that I am expecting). Is there is way to make those queries through FA?
We pretty much pass through the elasticsearch queries, letting ES do what it is good at. Modifying the elasticsearch index settings shouldn't cause any issues, but is not something we test.
Users are shared across tenants, so if you have one person logged in and they visit a different Fusionauth application url, they'll be automatically logged in again (without the need to auth again). I'm not sure that's what you want.
If you register a user to app A and then to app B, they'll be registered in both apps.
If you register a user to app A and then to app A again, I think you'd get an error message, but would have to try that out to be sure.
If you want to try this yourself, you could try richb201+1@gmail and richb201+2@gmail (anything after the + is treated as the same email address by gmail, but different email addresses by fusionauth).