Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NAMEX_API: Error processing MRAS get-profile request #23243

Open
eve-git opened this issue Sep 11, 2024 · 6 comments
Open

NAMEX_API: Error processing MRAS get-profile request #23243

eve-git opened this issue Sep 11, 2024 · 6 comments
Assignees
Labels
High Priority Names Team Name Request Name Examination Team NRO NRO Replacement

Comments

@eve-git
Copy link
Collaborator

eve-git commented Sep 11, 2024

Error found when retrieving MARS get-profile from NameRequest.
Here is the details of the error from Darci:

_I’ve found that when I am requesting NRs in Names Request, even though I know that the home jurisdiction and registration ID that I am entering does exist in our partners’ staging (TEST) environments, I am still getting no profile found. I can of course work around that and enter in information, but it should be pulling the profile.
I have two existing companies that I was testing with, and neither are pulling a get profile result in Names Request TEST:
• Alberta company registration ID 2010193437
• Quebec company registration ID 1170990601

I’ve been supplied both of these by our partners, and when I search them on the MRAS staging (TEST) hub, they do show up as active, so I’m not sure why their profile isn’t being pulled by Names Request.
Message in Names Request:_
image.png

@eve-git eve-git added the Names Team Name Request Name Examination Team label Sep 11, 2024
@eve-git
Copy link
Collaborator Author

eve-git commented Sep 11, 2024

The log indicate that MRAS getProfile responded without error.

2024-09-11 08:00:44,748 - namex - DEBUG in queue_util:queue_util.py:68 - send_name_request_state_msg: Published name request (NR 2991967) state change from APPROVED -> CONSUMED
Calling MRAS Jurisdictions API using [corp_num: 2010193437]
https://stagingapi.mrasservice.ca/api/v1/xpr/jurisdictions/2010193437
{'x-api-key': '344aab81-b585-4d13-b22b-25e3c054cc88-4acb19ee-ef18-4ec9-8bad-255881f45edf', 'Accept': 'application/xml'}
Valid jurisdiction IDs
['SK', 'AB', 'QC', 'MB']

Calling MRAS Profile API using [corp_num: 2010193437], [province: AB]
https://stagingapi.mrasservice.ca/api/v1/xpr/GetProfile/2010193437/AB
{'x-api-key': '344aab81-b585-4d13-b22b-25e3c054cc88-4acb19ee-ef18-4ec9-8bad-255881f45edf', 'Accept': 'application/xml'}

Probably the error from the last step: parsing the response XML to json.

@ozamani9gh
Copy link
Collaborator

for testing, please reach out to darci to get test data

@eve-git
Copy link
Collaborator Author

eve-git commented Sep 13, 2024

Darci will conduct the test.

The message from Darci:

I’ve been able to successfully pull in profiles for AB, MB and QC now (temporary fix by MRAS support for now) in TEST.
I would say we are good to push this to PROD any time.

@Mihai-QuickSilverDev
Copy link
Collaborator

  • Moving to Ready for Release as Legacy BA Team will conduct the Test.

@ozamani9gh
Copy link
Collaborator

@eve-git reach out to Darci to get the necessary test data or confirmation that she can test it and its working.

@eve-git
Copy link
Collaborator Author

eve-git commented Nov 20, 2024

Darci has tested (see her message above).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
High Priority Names Team Name Request Name Examination Team NRO NRO Replacement
Projects
None yet
Development

No branches or pull requests

3 participants