<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<p>There is something I clearly cannot figure out about the spring.schemas file. I looked at samples in the Shibboleth source code and it looks like a remote path on the left and a local path in the jar on the right, something like this:</p>
<p><br>
</p>
<p></p>
<p class="x_p1" style="margin-right:0px; margin-left:0px; font-size:12px; line-height:normal; font-family:Courier; color:rgb(59,35,34); background-color:rgb(215,211,183)">
<span class="x_s1" style="">http\://shibboleth.net/schema/idp/shibboleth-attribute-resolver.xsd = schema/shibboleth-attribute-resolver.xsd</span></p>
<br>
<p></p>
<p>I use the same format with the escaped ":", but no matter what, I get the blocked remote lookup warning. Either I do not get the syntax or there is some other thing I need to do to get Shibboleth to setup that remote location mapping to the jarfile's schema. </p>
<p><br>
</p>
<p><br>
</p>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> users <users-bounces@shibboleth.net> on behalf of Cantor, Scott via users <users@shibboleth.net><br>
<b>Sent:</b> Monday, March 6, 2023 1:10:43 PM<br>
<b>To:</b> Shib Users<br>
<b>Cc:</b> Cantor, Scott<br>
<b>Subject:</b> Re: Custom Dataconnector's Schema</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">It means you didn't have it correct originally and it's been loading it "remotely", though in your case it wasn't remote in a network sense. If you had stuck a remote URL in schemaLocation it would have happily resolved that, which is
why we fixed it to stop doing that.<br>
<br>
You have to fix your spring schema namespace mapping file to properly direct the value in the schemaLocation mapping into the classpath resource path you want it to use.<br>
<br>
Spring is badly broken in this area but in a nutshell it insists on using the schemaLocation to locate the schema based on the namespace and then (optionally) maps from that location to a resource to load if you want it to pull from a jar via the META-INF spring.schemas
file.<br>
<br>
We just fixed it so that it it doesn't work if you bypass spring.schemas by accident or on purpose.<br>
<br>
-- Scott<br>
<br>
<br>
-- <br>
For Consortium Member technical support, see <a href="https://shibboleth.atlassian.net/wiki/x/ZYEpPw">
https://shibboleth.atlassian.net/wiki/x/ZYEpPw</a><br>
To unsubscribe from this list send an email to users-unsubscribe@shibboleth.net<br>
</div>
</span></font>
</body>
</html>