Registrant: error on login to portal

[vohmar]

A user reported issues with logging into the portal for registrants. He has used the portal previously

log:

[11:22:13] <ratMin> Feb 28 22:40:09 reg-l-rant REGISTRANT[28116]: [registrant] [f54c3d58-b3d6-4f5f-8245-6c36337d367e] [217.159.129.139] #012
[11:22:16] <ratMin> NoMethodError (undefined method `element_children' for nil:NilClass):#012  app/models/soap/arireg.rb:99:in `associated_b
[11:22:20] <ratMin> usinesses'#012  app/models/business_registry_cache.rb:62:in `fetch_by_ident_and_cc'#012  app/models/business_registry_ca
[11:22:23] <ratMin> che.rb:49:in `fetch_associated_domains'#012  app/controllers/registrant/domains_controller.rb:58:in `domains'#012  app/c
[11:22:27] <ratMin> ontrollers/registrant/domains_controller.rb:7:in `block in index'#012  app/controllers/registrant/domains_controller.rb:
[11:22:30] <ratMin> 74:in `normalize_search_parameters'#012  app/controllers/registrant/domains_controller.rb:6:in `index'#012  config/initi
[11:22:34] <ratMin> alizers/eis_custom_flash.rb:9:in `call'

[artur-intech]

Where exactly did it happen? I don't see the url. Also, please provide plain log, the one provided is unreadable.

[artur-intech]

mobile-id

[artur-intech]

How many users experienced this issue? It seems like some error while trying to parse business registry's response. One of the possible reasons can be that the registry was unavailable for some time and during this time some unexpected response was generated.

Some folks report gem incompatible issues: savonrb/wasabi#61

[artur-intech]

To investigate this issue further I need to setup business registry access on localhost, which may be time consuming. Confirm this.

[teadur]

Bussiness registry access is whitelist based, so you cannot access it from your home ip.
In theory you could use our interna proxy for that ( would require vpn to be connected ) so it makes more sense to test/dev it in staging rather then "localhost"

[vohmar]

this seems to have been some temporary type of error, the user does not have this any more. But better error handling would still be nice if possible. May have been some error on SK's side.