Hot!OWA Agent 1.6 - not working after 6.2 upgrade

Author
dagfinn@bedsys.no
New Member
  • Total Posts : 4
  • Scores: 0
  • Reward points: 0
  • Joined: 2020/09/29 00:36:16
  • Status: offline
2020/09/29 01:14:17 (permalink)
0

OWA Agent 1.6 - not working after 6.2 upgrade

We had OWA Agent 1.6 working fine with Fortitoken Mobil and Fortitoken 200 HW on version 6.1.2-build 420
 
After upgrading to version 6.2 build 542 - the OWA Agent stopped working for all users.
The Logs or Debug Logs are not very informativ. 
2020-09-24 13:07:51,268 - REST API - information - Receiving HTTP POST request at "/api/v1/auth/" from "192.168.xx.xx": (API user=apiuser, username=xxxxx, token=573726)
2020-09-24 13:07:51,281 - REST API - warning - Invalid realm is replaced by 'myrealm'
2020-09-24 13:07:52,307 - REST API - warning - HTTP POST request from "192.168.xx.xx" failed for "/api/v1/auth/": User authentication failed (Response: HTTP 401, API user=apiuser, username=myrealm/xxxxx, token_code=573726)

I Have tried the same login with an API tester, without any problem.
 
I Created a new user and assigned a Fortitoken HW, then by magic it worked.  But I cant see any difference between the new user and all other remote users.
 
Any ideas here ? How to troubleshoot ?
 
#1

3 Replies Related Threads

    seadave
    Expert Member
    • Total Posts : 365
    • Scores: 58
    • Reward points: 0
    • Joined: 2004/11/03 18:02:09
    • Location: Seattle, WA
    • Status: offline
    Re: OWA Agent 1.6 - not working after 6.2 upgrade 2020/10/06 18:20:37 (permalink)
    0
    Any luck getting this to work?  Testing it on Exchange 2019 on-prem and I get a page error when I enable the plugin.  API and hostnames are properly configured per the instructions.
    #2
    dagfinn@bedsys.no
    New Member
    • Total Posts : 4
    • Scores: 0
    • Reward points: 0
    • Joined: 2020/09/29 00:36:16
    • Status: offline
    Re: OWA Agent 1.6 - not working after 6.2 upgrade 2020/10/28 06:23:51 (permalink)
    0
    We have 3 different Organization's in one Fortiauthenticator.  Mostly this works fine for authentications.
    When using tha OWA Agent 1.6 there is not possible to specify a Realm to use.
     
    In the Windows Agent this is possible.  Anyone knows how to enter a Realm in the OWA Agent.
     
    #3
    dagfinn@bedsys.no
    New Member
    • Total Posts : 4
    • Scores: 0
    • Reward points: 0
    • Joined: 2020/09/29 00:36:16
    • Status: offline
    Re: OWA Agent 1.6 - not working after 6.2 upgrade 2020/11/11 06:53:30 (permalink)
    0
    It's working in the latest version,  6.2.1 build 552 
    #4
    Jump to:
    © 2020 APG vNext Commercial Version 5.5