I have created two lambda functions
register
login
and both of them are getting triggered from respective "Http APIs" in the API gateway. I have set up the stage for both of them as prod. Now I want to call them using my custom subdomain e.g prodapi.mydomain.com by setting the path as "v1"
prodapi.mydomain.com/v1/register
prodapi.mydomain.com/v1/login
I am able to achieve it for a single API but when I try to do API mapping for the other one using the same path, it doesn't allow that and says "ApiMapping key already exists for this domain name".
Any suggestion on how to achieve this?
can you share the endpoint url, before adding the subdomain, and after adding the subdomain
And can you explain your endpoints, how it should look like before adding the subdomain and after
Related
I am working in Microservices architecture.
I need your guidance in my implementation that I am working correctly or not.
I and internal service [Property] which calls from API Gateway.
In Property service I am sending responses using API resources with paginate, now the issue is my property service returns its internal URL within paginate. How can I change this custom domain URL from property to API gateway?
Or if I am doing something wrong please guide me about that. How can I use/implement paginate in internal services with next page click and search features?
I want to update the domain URL in the above image.
Thanks
Laravel has withPath method for pagination since version 5.4.
You can set relative path or absolute url with this method.
I suggest you can send request with pagination base path and dynamically set inside microservice.
I'm trying to use the okta api. I was able to use the api to create an authorization server and access policy with my okta domain.
The problem started when I tried adding a rule to the policy. When I tried adding a rule with my regular okta domain which looks like this: dev-1345678.okta.com, I got a 200 response but no rule was actually added to the policy. I then checked the request through the browser when adding one through the api and noticed that they're using a different okta domain which looks like this: https://dev-1345678-admin.okta.com. Only when I used that domain did I get a 201 request instead of 200, and the rule was actually created.
How do I know when I need to use the domain with the "admin" in the url and when not?
I have an eco system that the gateway and federated services live. The problem is when the gateway starts it validates the services - to do this it needs to be authorised.
When a client is querying via federation gateway they supply a bearer token.
In both instances the request header authorization field is used.
I've read and reread the docs but I am unable to achieve this using different tokens for different actions.
Anyone any ideas or links to relevant docs?
Cheers
Rereading for the Xth time the solution is with the "buildService".
It is only called once for each implementing service. You can extend it and add whatever headers you need.
See here for docs + example:
enter link description here
Using Google Domains, I've set up a synthetic record to redirect foo.com -> www.foo.com. Just like in this example:
https://support.google.com/domains/answer/6346300?hl=en
However, it doesn't seem to work with https://foo.com.
How do I configure it so that the subdomain forward works with https as well?
To give it more context, I'm mapping my custom domain to a heroku app, so I've set up a CNAME record for www.foo.com, and would like https://foo.com to be mapped to https://www.foo.com
Before providing any input please confirm if you are using any pointing service?
If http://foo.com is working whereas https://foo.com is not then you may need any service like pointDNS or cloudflare.
i am new to WHMCS API and i just want call WHMCS API from my spring boot rest template and i am tired of adding my ip address to WHMCS->General Setting->Security->API IP Access Restriction.
According to WHMCS docs, it is a requirement:
API IP Access Restriction
Advanced. If using the WHMCS API from an off-server location, you must
specify the IP address here, otherwise access will be denied.
You can submit a feature request with your concerns so that they may consider an alternative in the future.
Edit:
According to WHMCS developer documentation, you can bypass IP Address restriction by using api access key in the configuration.php file:
$api_access_key = 'secret_key_passphrase_goes_here';
then access api with the following URL:
whmc-url.com/includes/api.php?action=xxxx&username=xxx&password=xxx&accesskey=secret_key_passphrase_goes_here