<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<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 name="x_Generator" content="Microsoft Word 15 (filtered medium)">
<style>
<!--
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
p.x_MsoNormal, li.x_MsoNormal, div.x_MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
a:x_link, span.x_MsoHyperlink
{color:blue;
text-decoration:underline}
a:x_visited, span.x_MsoHyperlinkFollowed
{color:#954F72;
text-decoration:underline}
.x_MsoChpDefault
{}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
div.x_WordSection1
{}
-->
</style>
<div lang="EN-US" link="blue" vlink="#954F72">
<div class="x_WordSection1">
<p class="x_MsoNormal">I just did a quick test using my iPhone, and it appears to work just fine. Using 2 strongSwan profiles, each profile has a different VPN cert, with different altNames in the cert. By changing the Remote ID on iOS I was able to authenticate
with each of the 2 profiles. </p>
<p class="x_MsoNormal"> </p>
<div style="border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="x_MsoNormal" style="border:none; padding:0in"><b>From: </b><a href="mailto:bls3427@outlook.com">bls s</a><br>
<b>Sent: </b>Friday, October 5, 2018 6:54 AM<br>
<b>To: </b><a href="mailto:matthieu.nantern@margo.com">Matthieu Nantern</a><br>
<b>Cc: </b><a href="mailto:users@lists.strongswan.org">users@lists.strongswan.org</a><br>
<b>Subject: </b>Re: [strongSwan] Ikev2 wildcards with MacOs clients</p>
</div>
<p class="x_MsoNormal"> </p>
</div>
</div>
<font size="2"><span style="font-size:11pt;">
<div class="PlainText">I haven't looked into this in detail, but could you use different VPN certs for each subnet? Each VPN cert would be in a different conn section, and they would have different altNames (SAN). If I understand the MacOS VPN config correctly
(looks a lot like iOS), when certs are installed onto MacOS, you can specify the Remote ID, which is the SAN that matches that of the VPN cert.<br>
<br>
From: Matthieu Nantern <matthieu.nantern@margo.com><br>
Sent: Thursday, October 4, 2018 11:31 PM<br>
To: bls3427@outlook.com<br>
Cc: users@lists.strongswan.org<br>
Subject: Re: [strongSwan] Ikev2 wildcards with MacOs clients<br>
<br>
We are using certificates (one for each client device) but I have 2 networks: n1 and n2. And I want that some users can access n1 and others n1 + n2.<br>
<br>
<br>
I wanted to make the distinction by using a conf like that:<br>
<br>
<br>
conn alice<br>
leftsubnet=10.1.0.10/32<br>
right=%any<br>
rightid="C=CH, O=Linux strongSwan, OU=Research, CN=*"<br>
auto=add<br>
<br>
conn venus<br>
leftsubnet=10.1.0.20/32<br>
right=%any<br>
rightid="C=CH, O=Linux strongSwan, OU=Accounting, CN=*"<br>
auto=add<br>
But unfortunately with MacOs client I don't have the Distinguished Names but only the FQDN:<br>
<br>
<br>
ikev2-pubkey[1216]: ESTABLISHED 2 minutes ago, 10.8.1.113[vpn.test.net]...213.41.12.162[firstname.lastname@test.com]<br>
ikev2-pubkey{2102}: INSTALLED, TUNNEL, reqid 325, ESP in UDP SPIs: c4d64307_i 0c4df008_o<br>
<br>
<br>
And if you compare that with the StrongSwan Android client:<br>
<br>
<br>
ikev2-pubkey[1217]: ESTABLISHED 4 seconds ago, 10.8.1.113[vpn.test.net]...213.41.12.162[C=FR, O=Test, OU=Prod, CN=firstname.lastname@test.com]<br>
ikev2-pubkey{2103}: INSTALLED, TUNNEL, reqid 326, ESP in UDP SPIs: c3b37b06_i be7247e0_o<br>
<br>
<br>
So I cannot route my users according to their certificates and I was wondering what can I do ?<br>
<br>
<br>
<br>
Le jeu. 4 oct. 2018 à 19:42, bls s <bls3427@outlook.com> a écrit :<br>
<br>
Someone will likely explain why using certificates sucks, but if you use certificates (one for each client device) you'll have fine-grained user access control (by revoking/deleting certs), and you don't need to list all the enabled certs anywhere in your config
file.<br>
From: Users <users-bounces@lists.strongswan.org> on behalf of Matthieu Nantern <matthieu.nantern@margo.com><br>
Sent: Thursday, October 4, 2018 8:41 AM<br>
To: users@lists.strongswan.org<br>
Subject: Re: [strongSwan] Ikev2 wildcards with MacOs clients<br>
<br>
Is it possible to have multiple email address in the “rightid“ parameter ? Maybe I can list all authorized users for each server instead of relying on Distinguished Names ?<br>
<br>
<br>
<br>
Le mer. 3 oct. 2018 à 08:42, Matthieu Nantern <matthieu.nantern@margo.com> a écrit :<br>
<br>
Hi !<br>
<br>
<br>
I installed StrongSwan to allow my users (mainly MacOs X clients) to use the native ikev2 authentication. Everything is working fine.<br>
<br>
<br>
Now I would like to implement something like that : <a href="https://www.strongswan.org/testing/testresults/ikev2/wildcards/index.html">
https://www.strongswan.org/testing/testresults/ikev2/wildcards/index.html</a> ; allowing some clients to access some network and not the others.<br>
<br>
<br>
Unfortunately I didn't see (or understand) the issue on that page (<a href="https://wiki.strongswan.org/projects/strongswan/wiki/AppleIKEv2Profile">https://wiki.strongswan.org/projects/strongswan/wiki/AppleIKEv2Profile</a>) :<br>
<br>
<br>
ASN.1 Distinguished Names can't be used as identities because the client currently sends them as identities of type FQDN.<br>
<br>
<br>
As a result when I put rightid in my configuration it's not working because MacOsX is only sending a fqdn (an email address in my case) and not the Distinguished Name.<br>
<br>
<br>
<br>
My question is how can allow (or deny) some network to some user?<br>
<br>
<br>
<br>
I have a file that associates email address to "role" but I don't know how to use it. Maybe a plugin?<br>
<br>
<br>
Any ideas/links?<br>
<br>
<br>
Thank you!<br>
<br>
--<br>
<br>
Matthieu Nantern<br>
<br>
<br>
--<br>
<br>
Matthieu Nantern<br>
SRE, Margo Bank<br>
+33683148506<br>
<br>
<br>
--<br>
<br>
Matthieu Nantern<br>
SRE, Margo Bank<br>
+33683148506</div>
</span></font>
</body>
</html>