Intermittent 500 Error in Digital Garden Test Environment
I am using the Digital Garden test environment provided by the Banno Digital Toolkit. Most of the time, the login functionality works fine. However, occasionally, I encounter a 500 Internal Server Error when trying to log in.
Segment API issues – Adding members to segment not getting reflected
I created segment from my local machine using Banno segment API. It created successfully and i was able to validate it in UI
Segment API issues – Adding members to segment not getting reflected
I created segment from my local machine using Banno segment API. It created successfully and i was able to validate it in UI
Segment API issues – Adding members to segment not getting reflected
I created segment from my local machine using Banno segment API. It created successfully and i was able to validate it in UI
Segment API issues – Adding members to segment not getting reflected
I created segment from my local machine using Banno segment API. It created successfully and i was able to validate it in UI
“Connection reset by peer” error when calling Banno token endpoint
Beginning on August 7, 2024 we have noticed an increase in “Connection reset by peer” errors when calling the Banno token endpoint. This appears to be intermittent. Not all users are experiencing this issue and the error will occasionally go away after navigating to the url a few times. For context, we have developed applications for external application buttons through banno olb. A user would click on a button from their online banking portal for something like “Rewards Dashboard” and the link would take them to a url similar to this – {{ specific_subdomain }}.account-hq.com/rewardsDashboard
. The “Connection reset by peer” error seems to occur during our attempt to fetch the Banno token on a call similar to this {base url}/a/consumer/api/v0/oidc/token
Test Data Accuracy in Garden FI
While pulling transaction data from the Consumer API (Garden FI), it appears that the activity is not a representative example of the different types of transactions described in the Type and SubType sections of the Transaction Details API Documentation. Basically, every draft is a Type of “Transfer” and SubType is “EFT” even when the transaction MEMO would suggest that it was a POS type of purchase. Is this just the nature of how test transaction data is populated in the sandbox or is this what we would see with a live FI? For example, is it safe to assume that a POS purchase with a debit card would be categorized as Type: POS and Subtype: PinDebit or are those not concrete rules?
‘Switch Profile’ option not working with plugins
We have a plugin where we are showing some user data and allowing single sign-on to the providers of that data. In our testing, some of our users that have multiple profiles were seeing issues of the original profile’s data being loaded into the plugin after they switch onto a different profile. The outcome is always the same, whichever profile was logged into first at the time they open the app/website is the profile they’ll see after they switch to a different one.
Switch Profile Plugin Logic
We have a plugin where we are showing some user data and allowing single sign-on to the providers of that data. In our testing, some of our users that have multiple profiles were seeing issues of the original profile’s data being loaded into the plugin after they switch onto a different profile. The outcome is always the same, whichever profile was logged into first at the time they open the app/website is the profile they’ll see after they switch to a different one.
Sending thousands Alerts
We want to send alert using institutions/{institutionId}/users/{userId}/alert/send/generic
to lets say 10k users and more in few minutes.
Will Admin API handle that amount of requests in very short time? Won’t our system be blocked because it is “spamming”?