You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
select Initiate SAML on the RealMe login service Messaging Test Site:SAML v2.0 AuthnRequest validation outcome interface
👀 Observe the test site's homepage again.
attempt to gain access to the CMS: /admin
👀 Observe the login form again
click Login under Login with RealMe® heading, again.
👀 Observe login form presented, message Unfortunately we're not able to log you in through RealMe right now. Please try again shortly.
Use the member authenticator this time (Email & Password), default admin credentials
👀 Observe a large PHP Emergency error: [Emergency] Uncaught BadMethodCallException: Object->__call(): the method 'getResponse' does not exist on 'SilverStripe\RealMe\Authenticator\LoginHandler' with an HTTP 500 response code.
Visit /admin - be logged in as normal.
You may have noticed between steps 7 and 8 above that the BackURL was altered from /admin/pages/ to /Secuirity/login/RealMe/acs. This triggers the manifestation, however this issue is really about the "not so nice" handling of an already authenticated session.
Alternate recreation steps:
Log in to CMS as default admin.
visit /Security/login
click the RealMe Login button.
👀 Observe a large PHP Emergency error: [Emergency] Uncaught BadMethodCallException: Object->__call(): the method 'getResponse' does not exist on 'SilverStripe\RealMe\Authenticator\LoginHandler' with an HTTP 500 response code.
'OneLogin SAML library did not successfully authenticate, but did not return a specific error',
RealMeException::NOT_AUTHENTICATED
);
}
Log messages give Error during RealMe authentication process. Code: 7, Message: OneLogin SAML library did not successfully authenticate, but did not return a specific error
Where Code 7 is PRIVATE_KEY_FILE_NOT_FOUND, where the code checks for code 8: SAML_RESPONSE_NOT_FOUND in what looks like an attempt to avoid this
Currently testing MTS, login type integration.
There is a
Default Admin
user, but that is all.Discovery path:
/admin
Login
underLogin with RealMe®
heading.Initiate SAML
on theRealMe login service Messaging Test Site
:SAML v2.0 AuthnRequest validation outcome
interface/admin
Login
underLogin with RealMe®
heading, again.Unfortunately we're not able to log you in through RealMe right now. Please try again shortly.
[Emergency] Uncaught BadMethodCallException: Object->__call(): the method 'getResponse' does not exist on 'SilverStripe\RealMe\Authenticator\LoginHandler'
with an HTTP 500 response code./admin
- be logged in as normal.You may have noticed between steps 7 and 8 above that the
BackURL
was altered from/admin/pages/
to/Secuirity/login/RealMe/acs
. This triggers the manifestation, however this issue is really about the "not so nice" handling of an already authenticated session.Alternate recreation steps:
/Security/login
Login
button.[Emergency] Uncaught BadMethodCallException: Object->__call(): the method 'getResponse' does not exist on 'SilverStripe\RealMe\Authenticator\LoginHandler'
with an HTTP 500 response code.The execution path comes through here
silverstripe-realme/src/Authenticator/LoginHandler.php
Line 100 in 3cdbc9d
down to here
silverstripe-realme/src/RealMeService.php
Lines 530 to 535 in 3cdbc9d
Log messages give
Error during RealMe authentication process. Code: 7, Message: OneLogin SAML library did not successfully authenticate, but did not return a specific error
Where
Code 7
isPRIVATE_KEY_FILE_NOT_FOUND
, where the code checks for code8
:SAML_RESPONSE_NOT_FOUND
in what looks like an attempt to avoid thissilverstripe-realme/src/RealMeService.php
Lines 574 to 582 in 3cdbc9d
The text was updated successfully, but these errors were encountered: