"Rejecting replayed message ID" for iOS Native Application when using webview element

[mattzard]

Thanks for your feedback so far. 

Just to add some more information to this, here are requests I made using
different devices. You can see the iOS Native Application has a duplicate
request causing my error:

*IOS NATIVE APPLICATION*

	2019-06-13
08:37:04|Shibboleth-TRANSACTION.AuthnRequest|||http://[REMOVED]/adfs/services/trust||||||urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect||||||
	2019-06-13
08:37:05|Shibboleth-TRANSACTION.AuthnRequest|||http://[REMOVED]/adfs/services/trust||||||urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect||||||
	2019-06-13
08:37:05|Shibboleth-TRANSACTION.Login|||http://[REMOVED]/adfs/services/trust||||||urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST|opensaml::SecurityPolicyException||||Mozilla/5.0
(iPhone; CPU iPhone OS 10_3_3 like Mac OS X) AppleWebKit/603.3.8 (KHTML,
like Gecko) Mobile/14G60|90.152.30.76
	2019-06-13
08:37:05|Shibboleth-TRANSACTION.Login||_480908d2f78dd413783090bd73f8f71a|http://[REMOVED]/adfs/services/trust|_d9dc9a39-27f0-4494-ad66-298b746f1f8f|urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport|2019-06-13T08:28:59|eduPersonPrincipalNameUnspecified(1),emailaddressUnspecified(1),firstnameUnspecified(1),lastnameUnspecified(1)||urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST||urn:oasis:names:tc:SAML:2.0:status:Success|||Mozilla/5.0
(iPhone; CPU iPhone OS 10_3_3 like Mac OS X) AppleWebKit/603.3.8 (KHTML,
like Gecko) Mobile/14G60|90.152.30.76

*ANDROID*

	2019-06-13
08:46:56|Shibboleth-TRANSACTION.AuthnRequest|||http://[REMOVED]/adfs/services/trust||||||urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect||||||
	2019-06-13
08:46:57|Shibboleth-TRANSACTION.Login||_0a090da5c4306f3af42de916aa2186d9|http://[REMOVED]/adfs/services/trust|_e12751d7-b982-4922-90c5-1a92f5d42a05|urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport|2019-06-13T08:38:29|eduPersonPrincipalNameUnspecified(1),emailaddressUnspecified(1),firstnameUnspecified(1),lastnameUnspecified(1)||urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST||urn:oasis:names:tc:SAML:2.0:status:Success|||Mozilla/5.0
(Linux; Android 9; Pixel 3 XL Build/PQ3A.190605.003; wv) AppleWebKit/537.36
(KHTML, like Gecko) Version/4.0 Chrome/74.0.3729.157 Mobile
Safari/537.36|90.152.30.51

*IOS SAFARI*

	2019-06-13
08:52:34|Shibboleth-TRANSACTION.AuthnRequest|||http://[REMOVED]/adfs/services/trust||||||urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect||||||
	2019-06-13
08:52:35|Shibboleth-TRANSACTION.Login||_30e71a52149124000972e3094c9c2f92|http://[REMOVED]/adfs/services/trust|_7d93ff24-84cd-4119-8912-42164f0f5625|urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport|2019-06-13T08:51:56|eduPersonPrincipalNameUnspecified(1),emailaddressUnspecified(1),firstnameUnspecified(1),lastnameUnspecified(1)||urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST||urn:oasis:names:tc:SAML:2.0:status:Success|||Mozilla/5.0
(iPhone; CPU iPhone OS 12_1_2 like Mac OS X) AppleWebKit/605.1.15 (KHTML,
like Gecko) Version/12.0 Mobile/15E148 Safari/604.1|34.253.190.39

Hopefully these Shibboleth transactional logs can help identify the issue?
Thanks!




--
Sent from: http://shibboleth.1660669.n2.nabble.com/Shibboleth-Users-f1660767.html