Skip to content

Latest commit

 

History

History
65 lines (36 loc) · 4.75 KB

FAQs.md

File metadata and controls

65 lines (36 loc) · 4.75 KB
Raw

ReBIT AA Specifications Update (Version 2.X) - FAQs

General FAQs

Q1: What is the significance of the ReBIT AA Specifications Version 2.0.0 update?

A1: ReBIT published a major update to the AA specifications in the form of Version 2.0.0, affecting the catalog of APIs that FIPs, AAs, and FIUs implement. This update comes with a deprecation plan for older versions and introduces changes to response body headers.

Q2: What are the key dates associated with the Version 2.0.0 update?

A2: The key dates include the Deprecation Date (Jan 7, 2024), Plan of Action starting from Jan 7, 2024, Decommission Date (May 12, 2024), and a Co-existence Period until the Decommission Date.

For FIP/FIU

Q3: How can a FIP/FIU perform UAT testing for the ReBIT 2.0 specs?

A3: After implementing the Rebit 2.0 specs, FIP/FIU should test in the UAT environment. For API callers, update the CR GET API interface to parse the baseurl attribute. For API providers, update the entity in UAT to indicate the base URL of version 2.x implementation. For more details on how to update, refer to this sheet

Q4: What steps should API callers take during UAT testing?

A4: API callers should update the interface with Sahamati to parse the baseurl attribute in the CR GET API response. Test parsing logic using a dummy AA entity (AA00023400) and fetch entity details from this sheet to begin testing with AAs.

Q5: How can API providers indicate readiness for production after UAT testing?

A5: API providers should update the existing entity in UAT to indicate the base URL of the version 2.x implementation. Test with AAs ready in UAT on V2.0 using this link. After successful testing, indicate readiness for production.

Q6: How can FIP/FIUs move to production after UAT testing?

A6: After UAT testing, FIP/FIUs must integrate the CR GET API V2.0, which returns both V1 and V2 base URLs. API is expected to go live on 25th Jan 2024, for more details, refer to this document. Once complete, request entry into the CR by sending the updated prod JSON to services@sahamati.org.in.

Q7: Where can details of certifiers for production implementation be found?

A7: Details of certifiers for certification of 2.x implementation can be found here. Entities are recommended to get their implementation certified before moving to production.

For AA

Q8: How can an AA perform UAT Testing for the ReBIT 2.0 specs?

A8: After implementing the Rebit 2.0 specs, the AA system must test its implementation in the UAT environment. Refer to this document for more details.

Q9: What steps should API callers take before UAT testing?

A9:

  • Develop parsing logic to parse the response from the CR GET API in UAT as per the format: baseurl:"v1:<url for v1>, v2:<url for v2>".
  • Test parsing logic using dummy FIP and FIU entities in the UAT CR with Entity IDs: FIP89545, FIU00, FIU00020001, FIPGSP001-23.

Q10: How can API providers indicate readiness for production after UAT testing?

A10:

  • Create a new entity in the UAT CR to indicate the base URL of version 2.x implementation.
  • Make changes directly using the AA Commons portal in the format: baseurl:"v1:<url for v1>, v2:<url for v2>".
  • Request an update to the status on this link by writing to kunal@sahamati.org.in.

Q11: What is the process for moving to production after UAT testing?

A11:

  • Integrate the CR GET API V2.0 that returns V1 and V2 base URLs for live entities on V2.
  • Request entry into the CR by sending the updated prod JSON to services@sahamati.org.in.
  • The GET API V2.0 will be in production starting Jan 25th, 2024.

Q12: Where can details of certifiers for production implementation be found?

A12: Details of certifiers for production implementation can be found here. Entities are recommended to get their implementation certified.