Finally after doing some research we updated the Tomcat from v9.0.33 to
9.0.43 and the issue seems to be solved. At least we tested with one
particular user that was having this problem almost all the time, and with
the Chrome throttling and we couldn't reproduce it again.
El viernes, 26 de
Denizg,
On my local, I might see an initial delay of at most 2s. Java does just in time
compiling, so initial access to some things will include compile time.
You can set the loggers to debug for as many systems as possible (spring prints
a LOT of logs) and see where the delays show up.
Another
Hi everybody,
I am making some progress in building an Apereo CAS demo server with
delegated authentication with SAML2 (for integrating with italian SPID
system).
I am testing against a test IDP instance. I have been able to
generate a compliant SP metadata file (although with some manual
Additional information: using the Chrome throttling, with a custom profile
entering ANY value for the upload speed (even 100Mb) the issue can be
reproduced.
Can anybody please test if it happens under this scenario?
El viernes, 26 de marzo de 2021 a las 10:19:48 UTC-3, Nicolás López
escribió:
If I use the 3G throttling in Chrome for log in I can reproduce the issue
consistently...now what should I do with this information? :D
Using firefox, even with the GPRS profile it logs in without any problem.
With the throttling you can just set upload/download max speed and latency,
it looks
If I use the 3G throttling for logging in I can reproduce the issue
consistently...now what should I do with this information? :D
With the throttling you can just set upload/download max speed and latency,
it looks so wierd.
El viernes, 26 de marzo de 2021 a las 7:01:39 UTC-3, Andy Ng escribió:
Hi Misagh,
I have been able to comply to the SHA-256 requirement by creating
certificates manually:
- Firstly I created the files saml-signing-cert-SAML2Client.crt,
saml-signing-cert-SAML2Client.key, saml-signing-cert-SAML2Client.pem with
openssl
- Then I created samlKeystore.jks
In our case we don't have a firewall blocking anything, we just have port
443 open and that's it. And it happens with Wi-Fi as well, nothing related
to the connection.
It happens only to some Chrome users, not all of them and not allways. But
for some of them it happens "almost" all the time.
Finally everything is working as expected. I've moved whole cas.properties
config to Vault, set up Redis to store Google Auth registered devices.
Now, I'm wondering how to make possible for end user add another device?
How to remove registered device? Any hints?
Thanks in advance
Regards
Hi,
I can't see an issue tracker on the CAS Github site, so I hope this is the
correct place to raise a bug instead. If there is a separate issue tracker
somewhere please let me know.
We are replacing an old CAS implementation with 6.3.2, and the new one uses
OAuth to delegate to Azure AD.
I am using cas overlay template (6.2.0). the cas server will be ready too
late (almost in 1 minutes), but that's not my real problem. when the
screens are opened for first time, the responses are slow, and the first
actions on the screens respond late.
For example, I open login screen for
Hi all,
I think I also am running out of idea, let see if the following would help
identify the issue:
1. Would it be your firewall blocking other browser but allow only
Firefox?
- You said using 4G will work but Wifi will not work. Usually company
firewall only block Wifi
Hi Andy,
thank you for your message.
So, I have tried with *cas.authn.attribute-repository.expiration-time=0*
Nothing change
I have tried with you lines on *attributeReleasePolicy*
Nothing change
I have tried with 6.3 version
Nothing change
I have tried just with the ligne below in
Hello,
We tried the 2 solutions but none worked. We don't have any issues if we're
connected on wifi, we only have the issue with 4G connection (smartphone with
4G or on computer with 4G shared connection)
We tried with version 6.1, 6.2 and 6.3.
Any other ideas ?
We are desperate.
14 matches
Mail list logo
