" /> WWE GWS User not found - Genesys CTI User Forum

Author Topic: WWE GWS User not found  (Read 2946 times)

Offline Mr.T

  • Newbie
  • *
  • Posts: 17
  • Karma: 3
WWE GWS User not found
« on: June 12, 2019, 07:21:34 PM »
Advertisement
Hello want to know if anyone found this issue before.

GWS installed ok (first install), its up and running.

When I open the login screen, and try to login with any ID, I am getting: "[b]Your login or password is incorrect.[/b]" for all agents.

Followed all documentation:

1- application.yaml defined to use WS_Cluster
2- voice feature enabled
3- person, AgentLogin, place, defined ok
4- WS_Cluster > interaction-workspace settings ok

when looking the "cloud.log" I see only:

[font=courier][b][color=red]c.g.cloud.data.FeatureRepository  User [test] not found[/color][/b][/font]

Full:
[code]
06/12/2019 15:58:25.365 DEBUG [] [] [] [RTRMonitoringScheduledExecutorService-pool-1-thread-12]    c.g.c.i.d.RuntimeNodesRepository  Successfully saved heartbeat qualifier [ANodes]:node [/US/192.168.0.21]:[1560355105364]
06/12/2019 15:58:26.215 DEBUG [] [] [] [qtp917578647-20]    c.g.cloud.data.FeatureRepository  User [test] not found
06/12/2019 15:58:26.215 WARN  [] [] [] [qtp917578647-20]    c.g.c.w.s.CloudWebBasicAuthenticationFilter  User [test] not found
[/code]

Am I missing something?

Thank you!
« Last Edit: June 12, 2019, 07:24:42 PM by Mr.T »

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: WWE GWS User not found
« Reply #1 on: June 13, 2019, 08:07:02 AM »
Try to synchronize WWE against Configuration Server using following cmd:

[code] curl http://WWE_IP:WWE_PORT/api/v2/ops/genesys-environments/synchronization -d '{"operationName":"EnforceSynchronization"}' -H "Content-Type: application/json" -X POST -v  -u username:password[/code]

Offline Mr.T

  • Newbie
  • *
  • Posts: 17
  • Karma: 3
Re: WWE GWS User not found
« Reply #2 on: June 13, 2019, 11:32:18 AM »
[quote author=Kubig link=topic=11356.msg51784#msg51784 date=1560413222]
Try to synchronize WWE against Configuration Server using following cmd:
[/quote]

Same authentication issue... tried default and other accounts same thing: [b]User [default] not found[/b]

[code]
* About to connect() to 192.168.0.21 port 8090 (#0)
*  Trying 192.168.0.21... connected
* Connected to 192.168.0.21 (192.168.0.21) port 8090 (#0)
* Server auth using Basic with user 'default'
> POST /api/v2/ops/genesys-environments/synchronization HTTP/1.1
> Authorization: Basic ZGVmYXVsdDpwYXNzd29yZA==
> User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.27.1 zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> Host: 192.168.0.21:8090
> Accept: */*
> Content-Type: application/json
> Content-Length: 42
>
< HTTP/1.1 403 Forbidden
< Date: Thu, 13 Jun 2019 08:29:02 GMT
< Content-Type: application/json
< Transfer-Encoding: chunked
<
* Connection #0 to host 192.168.0.21 left intact
* Closing connection #0
{"statusCode":20,"statusMessage":"Authentication failed: username and/or password is incorrect"}[root@genesys2 config]#
[/code]


[b]cloud.log[/b]
[code]
06/13/2019 08:25:36.817 DEBUG [] [] [] [RTRMonitoringScheduledExecutorService-pool-1-thread-14]    c.g.c.i.d.RTRMonitoringServiceDistributed  192.168.0.21:/US/192.168.0.21 already monitored []
06/13/2019 08:25:40.345 DEBUG [] [] [] [pool-9-thread-1]    c.g.c.v.a.e.t.TelephonyUserMonitorV2  Looking for user sessions to cleanup...
06/13/2019 08:25:41.638 DEBUG [] [] [] [RTRMonitoringScheduledExecutorService-pool-1-thread-1]    c.g.c.i.d.RuntimeNodesRepository  Successfully saved heartbeat qualifier [ANodes]:node [/US/192.168.0.21]:[1560414341636]
06/13/2019 08:25:42.656 DEBUG [] [qKk30Oatq/MavDS+5mNfFQ1gbg6fm8d1zzvdpgu6pegeh5x] [] [qtp225819303-23]  /api/v2/me subresources=features,devices,channels c.g.cloud.web.CustomScopeFilter http://192.168.0.21:8090/ui/ad/v1/index.html Secur
ity context is null or not authenticated, extracting contact center ID from the header
06/13/2019 08:25:46.637 DEBUG [] [] [] [RTRMonitoringScheduledExecutorService-pool-1-thread-2]    c.g.c.i.d.RuntimeNodesRepository  Successfully saved heartbeat qualifier [ANodes]:node [/US/192.168.0.21]:[1560414346636]
06/13/2019 08:25:51.519 DEBUG [] [] [] [RTRMonitoringScheduledExecutorService-pool-1-thread-11]    c.g.c.v.c.t.TelephonyContextCacheRefreshService  Refreshing cached telephony processing contexts
06/13/2019 08:25:51.529 DEBUG [] [] [] [RTRMonitoringScheduledExecutorService-pool-1-thread-11]    c.g.c.v.c.t.TelephonyContextCacheRefreshService  Refresh complete
06/13/2019 08:25:51.637 DEBUG [] [] [] [RTRMonitoringScheduledExecutorService-pool-1-thread-5]    c.g.c.i.d.RuntimeNodesRepository  Successfully saved heartbeat qualifier [ANodes]:node [/US/192.168.0.21]:[1560414351636]
06/13/2019 08:25:54.215 DEBUG [] [qKk30Oatq/MavDS+5mNfFQ1gbg6fm8d1zzvdpgu6pegeh5x] [] [qtp225819303-23]  /api/v2/me subresources=features,devices,channels c.g.c.v.c.t.c.ChannelRepository http://192.168.0.21:8090/ui/ad/v1/index.html Repos
itory is initialized
06/13/2019 08:25:56.648 DEBUG [] [] [] [RTRMonitoringScheduledExecutorService-pool-1-thread-1]    c.g.c.i.d.RuntimeNodesRepository  Successfully saved heartbeat qualifier [ANodes]:node [/US/192.168.0.21]:[1560414356645]
06/13/2019 08:26:01.647 DEBUG [] [] [] [RTRMonitoringScheduledExecutorService-pool-1-thread-3]    c.g.c.i.d.RuntimeNodesRepository  Successfully saved heartbeat qualifier [ANodes]:node [/US/192.168.0.21]:[1560414361636]
06/13/2019 08:26:02.369 DEBUG [] [] [] [qtp225819303-25]    c.g.cloud.data.FeatureRepository  User [default] not found
06/13/2019 08:26:02.373 WARN  [] [] [] [qtp225819303-25]    c.g.c.w.s.CloudWebBasicAuthenticationFilter  User [default] not found
06/13/2019 08:26:06.517 DEBUG [] [] [] [RTRMonitoringScheduledExecutorService-pool-1-thread-2]    c.g.c.v.g.c.VoiceEnvironmentsMonitoringService  a3da4bb5-d65f-4bc3-a113-7f5c1d730cca called ensureMonitored
06/13/2019 08:26:06.517 DEBUG [] [] [] [RTRMonitoringScheduledExecutorService-pool-1-thread-2]    c.g.c.v.g.c.VoiceEnvironmentsMonitoringService  a3da4bb5-d65f-4bc3-a113-7f5c1d730cca service not activated, repair monitoring skipped till
activated
[/code]

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: WWE GWS User not found
« Reply #3 on: June 13, 2019, 01:33:29 PM »
You have to use account configured within WWE configuration (application.yaml), not the Genesys one

Offline Mr.T

  • Newbie
  • *
  • Posts: 17
  • Karma: 3
Re: WWE GWS User not found
« Reply #4 on: June 13, 2019, 03:54:09 PM »
[quote author=Kubig link=topic=11356.msg51789#msg51789 date=1560432809]
You have to use account configured within WWE configuration (application.yaml), not the Genesys one
[/quote]

Would you mind to point where in the documentation I can find that?
Thank you very much!!!

Offline Mr.T

  • Newbie
  • *
  • Posts: 17
  • Karma: 3
Re: WWE GWS User not found
« Reply #5 on: June 13, 2019, 05:12:38 PM »
[quote author=Kubig link=topic=11356.msg51789#msg51789 date=1560432809]
You have to use account configured within WWE configuration (application.yaml), not the Genesys one
[/quote]

found the issue... "onPremiseSettings"  needs to be in first line of application.yml

Offline knupf

  • Newbie
  • *
  • Posts: 4
  • Karma: 0
Re: WWE GWS User not found
« Reply #6 on: May 27, 2020, 10:43:17 AM »
Hi at all,
i have a similar Problem.
In application.yaml the  section "onPremiseSettings" is on top.
When i start the gws, gws cannot to the confserv.

I found a hint in Genesys Docs for this behaviour:
drop the cassandra keyspace "sipfs", then creating the Cassandra keyspace again.

After this, the gws can connect to the confserv.

Extensions, Agent_Logins and RoutingPoints are imported.
But Places, Users not!

c.g.c.v.s.t.ImportPlacesFromCmeTaskV2  No places were found in configuration
c.g.c.v.s.t.ImportUsersFromCmeTaskV2  No users to import!

But users and places are still configured in cme!

When i restart the gws without drop keyspace sipfs and create again,
gws cannot connect to confserv again.

Does anybody have a hint for me?

Regards
Knupf