Problem connection IRIS to Atelier
I have a problem connecting IRIS to Atelier Webapplication.
IRIS Version: IRIS for UNIX (Red Hat Enterprise Linux for x86-64) 2019.1.1 (Build 609U) Thu Sep 12 2019 22:40:26 EDT
When I try to access Atelier API ( i.e. Webbrowser ) then I can not authorize.
Here is what it looks like:
URL: http://localhost:52773/api/atelier
.png)
I put in the valid credentials of a user with a %Developer Role but I am not able to authorize.
The api/atelier web application is enabled in the Management Portal.
I have this bevhavior only with the ReadHat Community Unix version of IRIS.
When I try the same with a Windows Community Version of IRIS on Windows 10 - I can successfully authorize and connect.
Anyone any idea ? Maybe it is a license problem but I have no valid license key to test :-(
Comments
Maybe it is a license problem but I have no valid license key to test :-(
You would need any license, and should be able to connect if you use IRIS Community Edition.
But you need any license, with a common version, without a license it will not work. You can get a preview license on WRC.
I have the IRIS Community Editionlicense for Red Hat. Funny is that the IRIS Windows Community Edition works like a charm.
Here is the license key for the Red Hat Edition. Everything looks good.
| License Capacity | InterSystems IRIS Community license |
| Customer Name | InterSystems IRIS Community |
| Order Number | 54702 |
| Expiration Date | 10/30/2021 |
| Authorization Key | 8116600000500000500008000084345EF8F2473A5F13003 Product=Server License Type=Concurrent User Server=Single Platform=IRIS Community License Units=5 Licensed Cores=8 Authorized Cores=8 Extended Features=3A5F1300 - Interoperability - BI User - BI Development - HealthShare - Analytics Run - Analytics Analyzer - Analytics Architect - NLP - HealthShare Foundation - Analytics VR Execute - Analytics VR Format - Analytics VR Data Define - InterSystems IRIS Non-Production |
Unfortunately I have no login for WRC and can not get a preview license to test.
Hello Robert, yes of course I tried this but unfortunately it does not work. Do you have a Windows version or a Red Hat Linux ?
After enabling Audit and enabling the specific Audit events I could see the reason for the login failures.
Error message: ERROR #800: Logins for Service %Service_WebGateway are disabled
Web Application: /api/atelier
After starting the WebGateway Service I was able to log in.
@Alexander Koblov : Thanks for the tip - I did this already but didn't enable the specific events. So I could see nothing. Thank you.
check license usage in SMP/Operations
Check CSP Session as well
In Security / Application force authentication not to lose licenses to Unknown user,
It is not to comfortable but may help.
BTW. my preview licenses had all features but NO users. I kicked them as useless.
Thank you Robert .
When I try to connect -- 4 licenses are free out of 5 and also the trick to In Security / Application didn't work.
Sorry. My DOCKER is a Windows version. Iris is Ubuntu.
So it is UBUNTU inside Windows.
Windows also worked for me - see my sentence in the description:
When I try the same with a Windows Community Version of IRIS on Windows 10 - I can successfully authorize and connect.
Thanks for your help.
mine is Windows.
I just tried it with the Symposium (Docker, UBUNTU) ==> Community Version + Key
| License Capacity | InterSystems IRIS Community license |
| Customer Name | InterSystems IRIS Community |
| Order Number | 54702 |
| Expiration Date | 10/30/2021 |
| Authorization Key |
8116600000500000500008000084345EF8F2473A5F13003 . . . . . . |
Atelier required a restart but then it worked.
WELL: default in Ubuntu / Docker : firewall off
I fear Red Hat is different. But my last Red Hat is 15 yrs back :-(
My personal decision was to move to Docker because it is really easy after 1/2 day playing with basics.
Hi Udo,
I tried it with my 1 year old Atelier installation.
Setup of a new sever connection.
The test showed me:
.png)
OK so I changed to PASSWORD only
.png)
AND the test worked OK. And access as well..
The best way to handle such problems is:
a) Enable Audit (System Administration -> Security -> Auditing) b) Enable logging of audit events LoginFailure and Protect (Configure System Events) c) Reproduce the error d) Check Audit database if it has any reported LoginFailure or Protect events. If yes -- check details of these events.