Additional Information about Notification Configuration

[MattMatt27]

I am hoping to learn a little more about how our notification system is currently working.

In our documentation, it claims that we are required to configure an allowed list of API_KEYS in the LAMP-app-gateway container and the PUSH_API_KEY environment variable of LAMP-server must be included in the list of allowed API_KEYS. That logic appears to have been implemented here: https://github.com/BIDMCDigitalPsychiatry/LAMP-app-gateway/blob/24e29f3837712160e934de0326f93b1da377b99e/app.js#L192 and here: https://github.com/BIDMCDigitalPsychiatry/LAMP-server/blob/fe6fe8df31dcaecd82481a99f2c1f4e317466c9d/src/utils/queue/PushNotificationQueue.ts#L27

In our existing environment those keys are not currently configured correctly, but the notifications are still working. I was wondering if there is workaround that is sending out notifications without hitting the push endpoint in the gateway. Would it be possible that redis or the ios/android implementations themselves are handling notifications in another way? In the LAMP-core-ios repo I found this section of code for example: https://github.com/BIDMCDigitalPsychiatry/LAMP-core-ios/blob/e53a9ce39ef59bcd65e7734a25c1628b47508ea3/mindLAMP/Push%20Notification/UserNotifications.swift#L15

There are no code change requests associated with this ticket. I am just looking for enough information on how notifications are configured so that I can update our notification documentation.

[ZCOEngineer]

Hi @MattMatt27 is this a separate LAMP server installation?

[MattMatt27]

This is for the LAMP server instance currently in use by our team in Docker. I believe it is running on code from the most recent release https://github.com/BIDMCDigitalPsychiatry/LAMP-server/releases/tag/2023.7.27 and not master if that is helpful context.