'Re: [Dev] SAML in publisher and publisher-new'

[prev in list] [next in list] [prev in thread] [next in thread] 

List: wsf-c-dev
Subject: Re: [Dev] SAML in publisher and publisher-new
From: Dushan Silva <dushans () wso2 ! com>
Date: 2019-06-19 10:14:03
Message-ID: CAO-u42y=gWHs=q4W_XPN8Y16xWd9KCh8BkuFWciWszZHumo+sw () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

Hi Yaswanth,

   1. Availability of SAML integration for `publisher-new`

SAML integration is available in the publisher-new however we have not
tested and documented it for APIM 3.0 yet.

On Wed, Jun 19, 2019 at 3:19 PM Yaswanth Narvaneni <
Yaswanth.Narvaneni@ril.com> wrote:

> Hello,
>
>
>
> We are exploring WSO2 API Manager 3.0 (built from sources)
>
> I have integrated an external IdP (not IS) with `publisher` and `store`
> via SAML..
>
>
>
> However, I have two blockers/concerns
>
>    1. Availability of SAML integration for `publisher-new`
>       1. I see that OAuth2 is under development for this, but don't see
>       SAML anywhere.
>       2. Is SAML in pipeline for publisher-new or its not in the roadmap
>       at all?
>    2. Just in time provisioning in `publisher` and `store`. (Could be out
>    of scope for this list)
>       1. I read online that for JIT provisioning, IS is a MUST.
>       2. However to create a login it feels like an over kill to install
>       the identity server.
>       3. Is there an alternative? I see JIT in Carbon Management Panel
>       for configuring external IdP, but doesn't seem to work
>
>
>
> It would be great if someone can throw some light on the above. Thank you.
>
>
>
> Regards,
>
> Yaswanth
>
>
> "*Confidentiality Warning*: This message and any attachments are intended
> only for the use of the intended recipient(s), are confidential and may be
> privileged. If you are not the intended recipient, you are hereby notified
> that any review, re-transmission, conversion to hard copy, copying,
> circulation or other use of this message and any attachments is strictly
> prohibited. If you are not the intended recipient, please notify the sender
> immediately by return email and delete this message and any attachments
> from your system.
>
> *Virus Warning:* Although the company has taken reasonable precautions to
> ensure no viruses are present in this email. The company cannot accept
> responsibility for any loss or damage arising from the use of this email or
> attachment."
> _______________________________________________
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>

-- 
Best Regards
Dushan Silva
Software Engineer

*WSO2, Inc. *

lean . enterprise . middleware
Mob: +94 774 979042

[Attachment #5 (text/html)]

<div dir="ltr"><div dir="ltr">Hi  Yaswanth,<div><br></div><div><ol start="1" type="1" \
style="margin-top:0cm"><li class="gmail-m_7791260061388106571MsoListParagraph" \
style="margin-left:0cm"><span lang="EN-US" style="font-size:11pt">Availability of \
SAML integration for `publisher-new`</span></li></ol><span \
style="font-size:14.6667px">SAML integration is available in the publisher-new \
however we have not tested and documented it for APIM 3.0 \
yet.</span></div></div><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Wed, Jun 19, 2019 at 3:19 PM Yaswanth Narvaneni &lt;<a \
href="mailto:Yaswanth.Narvaneni@ril.com">Yaswanth.Narvaneni@ril.com</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">

<div lang="EN-IN">
<div class="gmail-m_7791260061388106571WordSection1">
Hello, We are exploring WSO2 API \
Manager 3.0 (built from sources) I have integrated an external IdP (not IS) with \
`publisher` and `store` via SAML.. \
 However, I have two blockers/concerns \
<ol style="margin-top:0cm" start="1" type="1"> <li \
class="gmail-m_7791260061388106571MsoListParagraph" style="margin-left:0cm">Availability of SAML integration for \
`publisher-new`</li><ol style="margin-top:0cm" start="1" \
type="a"> <li class="gmail-m_7791260061388106571MsoListParagraph" \
style="margin-left:0cm">I see that OAuth2 \
is under development for this, but don't see SAML \
anywhere.</li><li \
class="gmail-m_7791260061388106571MsoListParagraph" style="margin-left:0cm">Is SAML in pipeline for publisher-new or its not \
in the roadmap at all?</li></ol> <li \
class="gmail-m_7791260061388106571MsoListParagraph" style="margin-left:0cm">Just in time provisioning in `publisher` and \
`store`. (Could be out of scope for this list)</li><ol \
style="margin-top:0cm" start="1" type="a"> <li \
class="gmail-m_7791260061388106571MsoListParagraph" style="margin-left:0cm">I read online that for JIT provisioning, IS is a \
MUST.</li><li \
class="gmail-m_7791260061388106571MsoListParagraph" style="margin-left:0cm">However to create a login it feels like an over \
kill to install the identity server.</li><li \
class="gmail-m_7791260061388106571MsoListParagraph" style="margin-left:0cm">Is there an alternative? I see JIT in Carbon \
Management Panel for configuring external IdP, but doesn't seem to \
work</li></ol> </ol>
 \
 It \
would be great if someone can throw some light on the above. Thank \
you. Regards, Yaswanth </div>
 &quot;Confidentiality Warning: \
This message and any attachments are intended only for the use of the intended \
recipient(s), are confidential and may be privileged. If you are not the intended \
recipient, you are hereby notified that any review, re-transmission, conversion to \
hard copy, copying, circulation or other use of this message and any attachments is \
strictly prohibited. If you are not the intended recipient, please notify the sender \
immediately by return email and delete this message and any attachments from your \
system. Virus \
Warning: Although the company has taken reasonable precautions to \
ensure no viruses are present in this email. The company cannot accept responsibility \
for any loss or damage arising from the use of this email or \
attachment.&quot;</div>

_______________________________________________<br>
Dev mailing list<br>
<a href="mailto:Dev@wso2.org" target="_blank">Dev@wso2.org</a><br>
<a href="http://wso2.org/cgi-bin/mailman/listinfo/dev" rel="noreferrer" \
target="_blank">http://wso2.org/cgi-bin/mailman/listinfo/dev</a><br> \
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" \
class="gmail_signature"><div dir="ltr"><div><div><span \
style="font-size:small;letter-spacing:normal;font-family:arial">Best \
Regards</span></div><div dir="ltr"><span \
style="font-size:small;letter-spacing:normal;font-family:arial">Dushan \
Silva</span><div style="font-family:sans-serif;font-size:small;letter-spacing:normal"><div \
style="font-family:arial">Software Engineer</div><div style="font-family:arial"><div \
style="font-family:arial,sans-serif;font-size:13px"><p style="margin:0px"><span \
style="font-size:10pt;font-family:Arial,sans-serif"><b>WSO2, Inc.  \
</b></span></p></div><div style="font-family:arial,sans-serif;font-size:13px"><p \
style="margin:0px"><span style="font-size:10pt;font-family:Arial,sans-serif">lean . \
enterprise . middleware  </span></p></div></div><div style="font-family:arial">Mob: \
+94 774 979042<br></div></div></div></div></div></div></div>

_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[prev in list] [next in list] [prev in thread] [next in thread] 