Styled personify error message + new membership check logic #71
Conversation
Activity logger + Custom auth verification
|
Build 244 |
|
Build 244 |
|
Build 245 |
|
Build 245 |
anpolimus
changed the title
| return FALSE; | ||
| } | ||
| $body = '<StoredProcedureRequest> | ||
| <StoredProcedureName>YSV_OpenY_Member_Access</StoredProcedureName> |
There was a problem hiding this comment.
So now only Silicon Valley can do SSO?
There was a problem hiding this comment.
This was discussed between You, me and SV team that we should have the same approach in the checking of membership status by using a custom procedure everywhere.
We Can change it to the OpenY_Member_Access, but in general it was approved as new approach for checking.
If this not a strategy for now, we have to understand how to organize this check.
There was a problem hiding this comment.
@anpolimus could you share SQL procedure in README then?
I'm fine with it, just wanted to make it flexible
There was a problem hiding this comment.
I don't have that SQL. I was introduced to API request details only.
I'll ask YMCASV team to share it.
...les/openy_gc_auth/modules/openy_gc_auth_personify/src/Controller/PersonifyAuthController.php
Outdated
Show resolved
Hide resolved
...les/openy_gc_auth/modules/openy_gc_auth_personify/src/Controller/PersonifyAuthController.php
Outdated
Show resolved
Hide resolved
…roller/PersonifyAuthController.php
No description provided.