01-03-2019 01:26 AM
I have a copy of Act Premium v21.0.295.0, Update 5 running successfully, but I am now trying to get the Act! Companion to access my self hosted installation.
I’ve got Act Web running and I can access it both internally and externally through the web browser at https://act.[mydomain].com/apfw/
I can access the web api, again both internally and externally at https://act.[mydomain].com/act.web.api/
I can log in successfully, both through the web interface and via the api: https://act.[mydomain].com/act.web.api/swagger/index.html (See attached screenshot)
I have a valid SSL cert.
However, when I try to use the Act! Companion mobile app, it will not let me connect. I get a “User Login failed” message. I am sure I am using the same username and password that I used for the web version, and I am using an "administrator" level username which has the access rights to the web api.
I was able to connect successfully with the Act! Companion to the trial database in the US.
I’m drawing blanks at this point and I don’t know what else to try to get the application working.
From the iis log files, I can see the following entries:
# successful login via the web api via web browser
2019-01-03 09:00:15 10.10.1.66 GET /act.web.api/authorize - 443 - 10.10.1.201 Mozilla/5.0+(Macintosh;+Intel+Mac+OS+X+10_12_6)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/71.0.3578.98+Safari/537.36 https://act.[mydomain].com/act.web.api/swagger/index.html 200 0 0 5791
# attempt to use act! companion to access the same instance with the same username and password
2019-01-03 09:05:00 10.10.1.66 GET /act.web.api/api/system - 443 - 10.10.1.201 Mozilla/5.0+(iPhone;+CPU+iPhone+OS+12_1+like+Mac+OS+X)+AppleWebKit/605.1.15+(KHTML,+like+Gecko)+Mobile/16B92/vhdouzcxhdrwpgqmzeqcxzztivyntvxz http://localhost:9595/login 200 0 0 179
2019-01-03 09:05:00 10.10.1.66 OPTIONS /act.web.api/authorize - 443 - 10.10.1.201 Mozilla/5.0+(iPhone;+CPU+iPhone+OS+12_1+like+Mac+OS+X)+AppleWebKit/605.1.15+(KHTML,+like+Gecko)+Mobile/16B92/vhdouzcxhdrwpgqmzeqcxzztivyntvxz http://localhost:9595/login 404 0 2 0
Does anyone have any suggestions on how I might be able to debug or solve this problem further?
Thanks for your help.
- Paul
01-03-2019 05:59 AM
Setup & configuration notes (just in case)
Requires an active Act! Premium subscription and use of either Act! API or Act! Connect Link depending on deployment method.
01-03-2019 06:09 AM
Hi, are you using a Iphone or a Android based phone/Tablet?
we found that there may be a issue with android
regards
Ingo Lange
01-03-2019 06:33 AM
01-03-2019 06:35 AM
01-15-2019 09:20 AM
01-31-2019 03:57 AM
02-06-2019 04:59 AM
Try the solution mentioned in this thread:
02-06-2019 08:56 AM
I've posted this in another thread, but wanted to make sure everyone was aware of how this can be resolved:
All,
I wanted to provide an update to this thread on this issue, and it's status.
The development teams for Act! Companion and the Act! API reviewed the issue, were able to reproduce and identified its root cause. The issue stemmed from a CORS implementation on the API, which changed with the last update. The issue has been resolved, and will be released with Act! Companion v2.4 (releases this month - February) and a new API build being released alongside it. You'll be notified of the new Act! Companion version via the Google/Apple app store's update feature. New versions of the API can be downloaded from https://developer.act.com/
In the interim the issue can be resolved by updating the webconfig file for Act!/API to include both http://localhost:9595 AND https://localhost:9595.
Please let us know if you have any additional questions. If you would like early access to Act! Companion v2.4 for this fix, please email your app store email address (Google Play or Apple), and we will add you to the beta to get an early version - my email address is jeff.hanrahan@swiftpage.com. Beta will be available early next week.
Regards,
Jeff Hanrahan
02-06-2019 08:31 PM - edited 02-06-2019 08:32 PM
> Try the solution mentioned in this thread:
I get an "access denied" trying to access that link.