-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Null value in exported file #66
Comments
I'm showing a few errors: debug from the first JS error:
// export SAMLTrace namespace to make ao. Request definitions available // Put functionality in out own namespace SAMLTraceIO = function() { SAMLTraceIO.prototype = {
}, 'serialize': function(exportResult) { 'getOutputFile': function(exportResult) { /**
}, 'restoreFromImport' : function(importedRequests, tracer, onError) {
} /**
SAMLTraceIO.ExportFilter.prototype = {
}, 'perform' : function(reqs) {
} and second:
// export SAMLTrace namespace to make ao. Request definitions available // Put functionality in out own namespace SAMLTraceIO = function() { SAMLTraceIO.prototype = {
}, 'serialize': function(exportResult) { 'getOutputFile': function(exportResult) { /**
}, 'restoreFromImport' : function(importedRequests, tracer, onError) {
} /**
SAMLTraceIO.ExportFilter.prototype = {
}, 'perform' : function(reqs) {
} |
Does this occur for each and every trace you try to export? Could you please try make a small trace. E.g. just trace the request to this issue. Is it exportable? I could very well imagine that there's a single request in your trace which causes the error. |
I receive this error on ANY export attempt, both Chrome and Firefox. This is why I think it's something to do with our Cylance policy that is preventing the export from completing |
I'm on a REALLY tight government workstation and even I can use SAML-tracer.. Ask yourself how you can rule out your environment, instead of asking the community to rule out an environment that's a complete black-box for them ;) |
Yep, as Tim said it's really hard to guess what the problem may be. 🤔 I think it's really worth a try disabling Cylance for a moment. |
That's what I was somewhat obscurely asking for in my initial post. Are there any paths your extensions runs from I can try to exclude from our EPP? |
What do you mean by paths? This add-on is all javascript.. |
I ask because EPPs can block scripts based upon policies, and I need the path the script runs from to exclude said script(s) |
You could try the following:
Good luck 😀👍 |
Did this work out for you, @michaellewis259? Or did you give up on it? 😕 |
Nothing seems to be working, no exclusion I make (that's acceptable from a security standpoint) helps. I'll just use a VM or something. I appreciate the assist, and sorry for the wasted time. |
Even though this issue is closed I just want to add that I have the exact same issue |
@si-heger Are you using the same security product as the OP? |
@tvdijen We are not using the same products but similar stuff like Crowdstrike Falcon and Tenable Nessus. Getting the code is difficult as I am not a programmer :) If you can send me an instruction on how to get more details I can do that |
See if you can get things to work by following @khlr 's suggestions. |
I have the same issue, on my VM, just normal windows 10 without any antivirus installed. on the saml-tracer, (f12), console>
Anyway , what I tested was : |
I was able to replicate this as well, based on what info @slowerogue provided above. I simply triggered an AuthnRequest to an IDP that had a self-signed certificate loaded. I was unable to export the AuthnRequest in SAML-Tracer. Even trying the export again after clicking "Accept Risk and Continue" I was unable to export. All of this testing was performed in my lab environment with no security solution in place, and given the issue seems to have cropped up for sites with self-signed certs (and hence the "Potential Security Risk" warning), I am going to venture and guess that this may be related to Firefox security impositions? I use SAML-Tracer frequently with in-progress or dev sites with self-signed HTTPS certificates, but I don't think I've ever tried exporting one of them. Strictly speaking, I'm not sure that this is 100% related to the issue as originally brought up by @michaellewis259, but it very well could be, and certainly does seem to be repeatable. My deep suspicion here is that this is the result of restrictions placed on the WebExtension when the security warning is triggered for the self-signed cert. |
I also just noticed that we're dead-threading here... I'm going to post my comment above on the open issue #69. |
I'm having issues with exporting the trace. It doesn't matter if I mask/exclude values or not, the resulting file shows as null. This is happening in both Firefox and Chrome, which leads me to believe there is something I need to allow with one of my security tools, but nothing is showing up in their various consoles. Do you have any ideas as to what is going on?
The text was updated successfully, but these errors were encountered: