<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D51Y000088PsnXSASOkta Classic EngineSingle Sign-OnAnswered2020-04-02T03:08:43.000Z2020-03-25T09:40:34.000Z2020-04-02T03:08:43.000Z

UriahO.10288 (Customer) asked a question.

How to fix parsing error using OKTA-SAMLToolkit 3.1.2 ?

I'm integrating a legacy in-house web app with OKTA. It is a java JSP/Servlet-based app running on tomcat.

I keep getting the exception:

com.okta.saml.SAMLException: Problem parsing the configuration.

at com.okta.saml.AbstractSAMLValidator.getConfiguration(AbstractSAMLValidator.java:32)

at com.okta.saml.AbstractSAMLValidator.getConfigurationFrom(AbstractSAMLValidator.java:49)

 

When running this code:

 

protected void doPost(HttpServletRequest request, HttpServletResponse response) throws IOException {

 

SAMLValidator validator = new OSGiSafeSAMLValidator();

Configuration conf = validator.getConfigurationFrom("****/config.xml");

 

---------------------

 

XML file:

 

<?xml version="1.0" encoding="UTF-8"?>

<configuration><applications><application>

<md:EntityDescriptor entityID="http://www.okta.com/exk4u4w9ge4vLvVso4x6" xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata"><md:IDPSSODescriptor WantAuthnRequestsSigned="false" protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol"><md:KeyDescriptor use="signing"><ds:KeyInfo xmlns:ds="http://www.w3.org/2000/09/xmldsig*"><ds:X509Data><ds:X509Certificate>MIIDpDCCAoygAwIBAgIGAXDxwSkFMA0GCSqGSIb3DQEBCwUAMIGSMQswCQYDVQQGEwJVUzETMBEG

  A1UECAwKQ2FsaWZvcm5pYTEWMBQGA1UEBwwNU2FuIEZyYW5jaXNjbzENMAsGA1UECgwET2t0YTEU

  MBIGA1UECwwLU1NPUHJvdmlkZXIxEzARBgNVBAMMCmRldi04NDQ1NzYxHDAaBgkqhkiG9w0BCQEW

  DWluZm9Ab2t0YS5jb20wHhcNMjAwMzE5MDc0NDMyWhcNMzAwMzE5MDc0NTMyWjCBkjELMAkGA1UE

  BhMCVVMxEzARBgNVBAgMCkNhbGlmb3JuaWExFjAUBgNVBAcMDVNhbiBGcmFuY2lzY28xDTALBgNV

  BAoMBE9rdGExFDASBgNVBAsMC1NTT1Byb3ZpZGVyMRMwEQYDVQQDDApkZXYtODQ0NTc2MRwwGgYJ

  KoZIhvcNAQkBFg1pbmZvQG9rdGEuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA

  jvcKh+o1ZBHjIX71mAY2cuCUoFjJrCDXEQcpYsnJHDvf8fxSGEVI3+kqUvdZtnErJG45YVbn/wh9

  n6OrR/IMhadPi7X3QP/iVX//UMLgkdSCcZPAdqMzsD/I1ZW7RXrYTt+6A82cVxN3slUHOfbAimwS

  Z3f+n9bU8t7UW7ZiYsGZYRysol+FGPJkvDpGnWklIPskxbuDgrp60Eg8kKUNlNMLCApy1S4P8XUd

  xsT8i1BrGjVdwaFp9iSkRWgVdW+zBALPT+cXIJ3V5VYEpfmHK5tL1qpA5f78AwAsztaZxQjv8/gN

  yvdmvfpCjFmIQ2FdLtq4okz2FmOUIOG4dTW+7QIDAQABMA0GCSqGSIb3DQEBCwUAA4IBAQB1Vigt

  1HG68msH7BS7SE4i5O5coT0jRd0/urtqlBaYFTx57WUeg6mfMR0okiZHCsr02KXvjE3stjOlKLUg

  5UtWaESDXMGYGHbXKmY97M5LZg7n+A7pBWrxf1e/27pp0smU/EVEHlcvcYnpXvdBl7YhVhzbD7+6

  mrr0HGe3hgsL8G6EMfKqkO1ltKmRBlMg4byrhZt58zCt11E9aW3IS7NQHFSJUqb8BtwQ28nOSISn

  VSMRcFhy3h0L3NeTdED43t32KGh39KvfsfyvUizN0kpGk/D0VndclxxEW2HnQ5/wuRQO+N+Qpfee

  JYJ7Q97gY4aXazIWQ2iy9jYcT5GJ12yu</ds:X509Certificate></ds:X509Data></ds:KeyInfo></md:KeyDescriptor><md:NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress</md:NameIDFormat><md:SingleSignOnService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://dev-844576.okta.com/app/redislabsdev844576_localbo_2/exk4u4w9ge4vLvVso4x6/sso/saml"/><md:SingleSignOnService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" Location="https://dev-844576.okta.com/app/redislabsdev844576_localbo_2/exk4u4w9ge4vLvVso4x6/sso/saml"/></md:IDPSSODescriptor></md:EntityDescriptor>

</application></applications></configuration>


  • Hey there! Sorry for the lack of response here on the Discussions forum. If you’re still looking for an answer, I would recommend checking out our Developer resources, including the Developer Forum (https://devforum.okta.com/) and documentation. If you are unable to find the solutions you're looking for there, we would encourage you to contact our dedicated Developer Support team at developers@okta.com, and they will be able to help you out.

    Expand Post
This question is closed.
Loading
How to fix parsing error using OKTA-SAMLToolkit 3.1.2 ?