Uploaded image for project: 'CloverDX'
  1. CloverDX
  2. CLO-18910

Facilitate SAML debugging

    XMLWordPrintable

    Details

    • Story Points:
      1
    • Branch:
    • QA Testing:
      UNDECIDED
    • Sprint:
      Magenta Sprint 23, Magenta Sprint 24, Magenta Sprint 25

      Description

      Run SAML with CloverDX Server can be difficult. Debugging can help a customer to find out what is wrong. But it is hard to set it up.
      To facilitate that we might make some changes:

      1. remove com.cloveretl.server.auth.SamlServlet from obfuscation
      2. add a new SAML log4j2 appender
                       <RollingFile name="samlAppender"
        			fileName="${sys:clover.clover.home}/cloverlogs/saml.log"
        			filePattern="${sys:clover.clover.home}/cloverlogs/saml.log.%i">
        			<PatternLayout pattern="%d{yyyy-MM-dd HH:mm:ss,SSS} %-5p %X{IP} %m%n" charset="UTF-8" />
        			<Policies>
        				<SizeBasedTriggeringPolicy size="5MB" />
        			</Policies>
        			<DefaultRolloverStrategy max="10" />
        		</RollingFile>
        
                        <Logger name="com.cloveretl.server.auth.SamlServlet" level="debug" additivity="false">
        			<AppenderRef ref="samlAppender" />
        		</Logger>
        		
        		<Logger name="com.onelogin.saml2" level="debug" additivity="false">
        			<AppenderRef ref="samlAppender" />
        		</Logger>
        

        Attachments

          Activity

            People

            Assignee:
            reichmanf Filip Reichman
            Reporter:
            reichmanf Filip Reichman
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: