Developing a custom Oracle node, my credential test function isn’t detected. Example with new identifiers:
credSetup: { checkFunc: 'confirmConn' },
operations: { confirmConn: async () => { /* implement logic */ } }
What might be misconfigured?
I’ve encountered a similar issue when working on custom nodes. In my experience, the problem was often due to minor misconfigurations in the credential identifier mappings. It’s essential to verify that the naming of the testing function in your credential setup matches exactly with what you define in your operations. During one project, I found that even a slight mismatch or an omission in the file that aggregates credential definitions could cause the test function not to be detected. Rechecking the consistency across your configuration files might resolve the problem.
I once ran into a similar problem while testing custom credentials for a database integration. It turned out that the configuration’s function mapping was subtly off. I discovered that even minor mistakes, such as a typo in the function name or an unexpected case difference in how the identifier was defined, can lead to the credential test function not being recognized. Including debugging logs during initialization helped me pinpoint the misconfiguration. It might be useful to cross-reference your device’s loading sequence with the documentation to verify that every mapping and naming convention aligns perfectly.
hey liam, i had a similar issue before. check that you’re using the exact same naming inc your configuration and function files. even a slight typo or case error might be the cause.