04-05-2017 12:34 AM
I can log into the trial account hosted at.
https://usp1-iis-05.hosted1.act.com/xxxxxx
When I try to login to web api I get
{
"message": "Unauthorized",
"exceptionMessage": "Could not find any database named 'xxxxxx' configured to be exposed for web access",
"exceptionType": "System.UnauthorizedAccessException",
"stackTrace": " at act.web.api.Auth.ActConnector.CreateInstances(String serverAlias, String database)\r\n at act.web.api.Auth.ActConnector.Connect(AuthenticationMechanisms mechanism, String username, String password, String server, String database)\r\n at act.web.api.Security.AuthMessageHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)"
}
How do I configure the database to be exposed for web access?
Thanks
Keith
04-05-2017 02:36 AM
Thanks for the reply,
On Cloud each site has the own specific web.api link for example: https://usp1-iis-05.hosted1.act.com/SITENAMEHERE-api/act.web.api/
you will need to include: -api/act.web.api/ to the end of the website from here you can add the swagger/index.html#/ if you would like to login and receive a Bearer Token.
Hope this clears it up for you.
04-05-2017 01:58 AM
Hi Keith,
I would like to know which web.api service you are to logging into? (Act contact link / Zapier) as from starting a trial the web.api will be active and the database available to be connected to.
Thanks
Daniel Horn.
04-05-2017 02:10 AM
I imagine it's the standard Premium Web Cloud as documented here.
https://usp1-iis-05.hosted1.act.com/Act.Web.API/swagger/index.html
I can confirm using the same html get method I was able to log into our corporate server.
Thanks Daniel
Keith
04-05-2017 02:36 AM
Thanks for the reply,
On Cloud each site has the own specific web.api link for example: https://usp1-iis-05.hosted1.act.com/SITENAMEHERE-api/act.web.api/
you will need to include: -api/act.web.api/ to the end of the website from here you can add the swagger/index.html#/ if you would like to login and receive a Bearer Token.
Hope this clears it up for you.
04-05-2017 03:19 PM
Thanks Daniel.
Adding /SITENAME-api/ to the url resolved the issue for me.
Cheers
Keith