You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by "HOUNGBE, Fabrice (MTL)" <Fa...@bdc.ca.INVALID> on 2023/11/14 18:25:25 UTC
Integrate ActiveMQ classic version with Ldap for web console access
Hi folks,
Does anyone implement web console access integration with Ldap for ActiveMQ classic edition ?
I know that the web console configuration is offered using jetty but Im having hard time updating jetty.xml to be able to integrate the web console access with Ldap.
Any help will be really appreciated.
Thks
Fabrice Houngbe
Spécialiste, Technologies | Technology Specialist
T 514-807-6916 C 438-686-4037
[cid:image001.jpg@01DA16FD.B174CDD0]<http://www.bdc.ca/FR/Pages/accueil.aspx?utm_campaign=signature&utm_medium=email&utm_source=signature>
bdc.ca<http://www.bdc.ca/FR/Pages/accueil.aspx?utm_campaign=signature&utm_medium=email&utm_source=signature>
[cid:image002.jpg@01DA16FD.B174CDD0]<http://www.bdc.ca/facebook> [cid:image003.jpg@01DA16FD.B174CDD0] <http://www.bdc.ca/twitter> [cid:image004.jpg@01DA16FD.B174CDD0] <http://www.bdc.ca/linkedin> [cid:image005.jpg@01DA16FD.B174CDD0] <http://www.bdc.ca/youtube> [cid:image006.jpg@01DA16FD.B174CDD0] <https://www.instagram.com/bdc_ca/>
Information confidentielle : Le présent message, ainsi que tout fichier qui y est joint, est (sont) envoyé(s) à l'intention exclusive de son ou (ses) destinataire(s); il est de nature confidentielle et peut faire l'objet d'une information privilégiée. Nous avisons toute personne autre que le destinataire prévu que tout examen, réacheminement, impression, copie, distribution ou toute autre utilisation de ce message et tout document joint est (sont) strictement interdit(s). Si vous n'êtes pas le destinataire prévu, veuillez en aviser immédiatement l'expéditeur par retour de courriel et supprimer ce message et tout document joint de votre système. Merci!
Gérez vos abonnements aux communications de BDC.<https://www.bdc.ca/fr/articles-outils/boite-outils-entrepreneur/publications/formulaire-abonnement?utm_medium=email&utm_source=signature&utm_campaign=email-footer-disclaimer_fr>
(Veuillez noter que vous continuerez de recevoir les messages électroniques non commerciaux nécessaires à votre relation d'affaires avec BDC.)
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, retransmission, 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. Thank you!
Manage your subscriptions to BDC messages.<https://www.bdc.ca/en/articles-tools/entrepreneur-toolkit/publications/subscribe?utm_medium=email&utm_source=signature&utm_campaign=email-footer-disclaimer_en>
(Please note that you will continue to receive non-commercial electronic messages necessary for your business relationship with BDC.)
Re: Integrate ActiveMQ classic version with Ldap for web console access
Posted by Matt Pavlovich <ma...@gmail.com>.
… but you should use JB’s answer of using a separate JAAS realm for Jetty vs the 5.x-era approach.
> On Nov 15, 2023, at 8:46 AM, Matt Pavlovich <ma...@gmail.com> wrote:
>
> Hi Simon-
>
> Yes! The examples/conf folder in 6.0.0 contains the 5.x era configs for jetty to revert back to dedicated JAAS for jetty-layer.
>
> Thanks,
> Matt Pavlovich
>
>> On Nov 14, 2023, at 10:41 PM, Simon Lundström <si...@su.se.INVALID> wrote:
>>
>> Morning Matt,
>>
>> Is it possible to still separate auth[NZ] for web and messaging layer in
>> 6.x?
>>
>> People tend to connect to the web console and machines are using the
>> messaging layer.
>>
>> BR,
>> - Simon
>>
>> On Tue, 2023-11-14 at 20:20:42 +0100, Matt Pavlovich wrote:
>>> Hi Fabrice-
>>>
>>> For ActiveMQ 5.x, the web console access is managed by Jetty in a separate password store. Following Jetty instructions for configuring LDAP and group permissions.
>>>
>>> Ref: https://eclipse.dev/jetty/javadoc/jetty-9/org/eclipse/jetty/jaas/spi/LdapLoginModule.html
>>>
>>> Note: For ActiveMQ 6.x (release vote is underway this week), the web and messaging layers are setup to share the same authentication source (aka JAAS realm), and the setup would be shared. Follow the ActiveMQ LDAP setup and both messaging and web layer services will share the same authentication source.
>>>
>>> Hope this helps,
>>> Matt Pavlovich
>>>
>>>> On Nov 14, 2023, at 12:25 PM, HOUNGBE, Fabrice (MTL) <Fa...@bdc.ca.INVALID> wrote:
>>>>
>>>> Hi folks,
>>>> Does anyone implement web console access integration with Ldap for ActiveMQ classic edition ?
>>>> I know that the web console configuration is offered using jetty but Im having hard time updating jetty.xml to be able to integrate the web console access with Ldap.
>>>> Any help will be really appreciated.
>>>> Thks
>>>>
>>>> Fabrice Houngbe
>>>> Spécialiste, Technologies | Technology Specialist
>>>> T 514-807-6916 C 438-686-4037
>>>>
>>>> <http://www.bdc.ca/FR/Pages/accueil.aspx?utm_campaign=signature&utm_medium=email&utm_source=signature>
>>>>
>>>> bdc.ca <http://www.bdc.ca/FR/Pages/accueil.aspx?utm_campaign=signature&utm_medium=email&utm_source=signature>
>>>>
>>>> <http://www.bdc.ca/facebook> <http://www.bdc.ca/twitter> <http://www.bdc.ca/linkedin> <http://www.bdc.ca/youtube> <https://www.instagram.com/bdc_ca/>
>>>>
>>>>
>>>> Information confidentielle : Le présent message, ainsi que tout fichier qui y est joint, est (sont) envoyé(s) à l'intention exclusive de son ou (ses) destinataire(s); il est de nature confidentielle et peut faire l'objet d'une information privilégiée. Nous avisons toute personne autre que le destinataire prévu que tout examen, réacheminement, impression, copie, distribution ou toute autre utilisation de ce message et tout document joint est (sont) strictement interdit(s). Si vous n'êtes pas le destinataire prévu, veuillez en aviser immédiatement l'expéditeur par retour de courriel et supprimer ce message et tout document joint de votre système. Merci!
>>>> Gérez vos abonnements aux communications de BDC. <https://www.bdc.ca/fr/articles-outils/boite-outils-entrepreneur/publications/formulaire-abonnement?utm_medium=email&utm_source=signature&utm_campaign=email-footer-disclaimer_fr>
>>>> (Veuillez noter que vous continuerez de recevoir les messages électroniques non commerciaux nécessaires à votre relation d’affaires avec BDC.)
>>>>
>>>> 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, retransmission, 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. Thank you!
>>>> Manage your subscriptions to BDC messages. <https://www.bdc.ca/en/articles-tools/entrepreneur-toolkit/publications/subscribe?utm_medium=email&utm_source=signature&utm_campaign=email-footer-disclaimer_en>
>>>> (Please note that you will continue to receive non-commercial electronic messages necessary for your business relationship with BDC.)
>>>
>
Re: Integrate ActiveMQ classic version with Ldap for web console access
Posted by Matt Pavlovich <ma...@gmail.com>.
Hi Simon-
Yes! The examples/conf folder in 6.0.0 contains the 5.x era configs for jetty to revert back to dedicated JAAS for jetty-layer.
Thanks,
Matt Pavlovich
> On Nov 14, 2023, at 10:41 PM, Simon Lundström <si...@su.se.INVALID> wrote:
>
> Morning Matt,
>
> Is it possible to still separate auth[NZ] for web and messaging layer in
> 6.x?
>
> People tend to connect to the web console and machines are using the
> messaging layer.
>
> BR,
> - Simon
>
> On Tue, 2023-11-14 at 20:20:42 +0100, Matt Pavlovich wrote:
>> Hi Fabrice-
>>
>> For ActiveMQ 5.x, the web console access is managed by Jetty in a separate password store. Following Jetty instructions for configuring LDAP and group permissions.
>>
>> Ref: https://eclipse.dev/jetty/javadoc/jetty-9/org/eclipse/jetty/jaas/spi/LdapLoginModule.html
>>
>> Note: For ActiveMQ 6.x (release vote is underway this week), the web and messaging layers are setup to share the same authentication source (aka JAAS realm), and the setup would be shared. Follow the ActiveMQ LDAP setup and both messaging and web layer services will share the same authentication source.
>>
>> Hope this helps,
>> Matt Pavlovich
>>
>>> On Nov 14, 2023, at 12:25 PM, HOUNGBE, Fabrice (MTL) <Fa...@bdc.ca.INVALID> wrote:
>>>
>>> Hi folks,
>>> Does anyone implement web console access integration with Ldap for ActiveMQ classic edition ?
>>> I know that the web console configuration is offered using jetty but Im having hard time updating jetty.xml to be able to integrate the web console access with Ldap.
>>> Any help will be really appreciated.
>>> Thks
>>>
>>> Fabrice Houngbe
>>> Spécialiste, Technologies | Technology Specialist
>>> T 514-807-6916 C 438-686-4037
>>>
>>> <http://www.bdc.ca/FR/Pages/accueil.aspx?utm_campaign=signature&utm_medium=email&utm_source=signature>
>>>
>>> bdc.ca <http://www.bdc.ca/FR/Pages/accueil.aspx?utm_campaign=signature&utm_medium=email&utm_source=signature>
>>>
>>> <http://www.bdc.ca/facebook> <http://www.bdc.ca/twitter> <http://www.bdc.ca/linkedin> <http://www.bdc.ca/youtube> <https://www.instagram.com/bdc_ca/>
>>>
>>>
>>> Information confidentielle : Le présent message, ainsi que tout fichier qui y est joint, est (sont) envoyé(s) à l'intention exclusive de son ou (ses) destinataire(s); il est de nature confidentielle et peut faire l'objet d'une information privilégiée. Nous avisons toute personne autre que le destinataire prévu que tout examen, réacheminement, impression, copie, distribution ou toute autre utilisation de ce message et tout document joint est (sont) strictement interdit(s). Si vous n'êtes pas le destinataire prévu, veuillez en aviser immédiatement l'expéditeur par retour de courriel et supprimer ce message et tout document joint de votre système. Merci!
>>> Gérez vos abonnements aux communications de BDC. <https://www.bdc.ca/fr/articles-outils/boite-outils-entrepreneur/publications/formulaire-abonnement?utm_medium=email&utm_source=signature&utm_campaign=email-footer-disclaimer_fr>
>>> (Veuillez noter que vous continuerez de recevoir les messages électroniques non commerciaux nécessaires à votre relation d’affaires avec BDC.)
>>>
>>> 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, retransmission, 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. Thank you!
>>> Manage your subscriptions to BDC messages. <https://www.bdc.ca/en/articles-tools/entrepreneur-toolkit/publications/subscribe?utm_medium=email&utm_source=signature&utm_campaign=email-footer-disclaimer_en>
>>> (Please note that you will continue to receive non-commercial electronic messages necessary for your business relationship with BDC.)
>>
Re: Integrate ActiveMQ classic version with Ldap for web console access
Posted by Simon Lundström <si...@su.se.INVALID>.
Morning Matt,
Is it possible to still separate auth[NZ] for web and messaging layer in
6.x?
People tend to connect to the web console and machines are using the
messaging layer.
BR,
- Simon
On Tue, 2023-11-14 at 20:20:42 +0100, Matt Pavlovich wrote:
> Hi Fabrice-
>
> For ActiveMQ 5.x, the web console access is managed by Jetty in a separate password store. Following Jetty instructions for configuring LDAP and group permissions.
>
> Ref: https://eclipse.dev/jetty/javadoc/jetty-9/org/eclipse/jetty/jaas/spi/LdapLoginModule.html
>
> Note: For ActiveMQ 6.x (release vote is underway this week), the web and messaging layers are setup to share the same authentication source (aka JAAS realm), and the setup would be shared. Follow the ActiveMQ LDAP setup and both messaging and web layer services will share the same authentication source.
>
> Hope this helps,
> Matt Pavlovich
>
> > On Nov 14, 2023, at 12:25 PM, HOUNGBE, Fabrice (MTL) <Fa...@bdc.ca.INVALID> wrote:
> >
> > Hi folks,
> > Does anyone implement web console access integration with Ldap for ActiveMQ classic edition ?
> > I know that the web console configuration is offered using jetty but Im having hard time updating jetty.xml to be able to integrate the web console access with Ldap.
> > Any help will be really appreciated.
> > Thks
> >
> > Fabrice Houngbe
> > Spécialiste, Technologies | Technology Specialist
> > T 514-807-6916 C 438-686-4037
> >
> > <http://www.bdc.ca/FR/Pages/accueil.aspx?utm_campaign=signature&utm_medium=email&utm_source=signature>
> >
> > bdc.ca <http://www.bdc.ca/FR/Pages/accueil.aspx?utm_campaign=signature&utm_medium=email&utm_source=signature>
> >
> > <http://www.bdc.ca/facebook> <http://www.bdc.ca/twitter> <http://www.bdc.ca/linkedin> <http://www.bdc.ca/youtube> <https://www.instagram.com/bdc_ca/>
> >
> >
> > Information confidentielle : Le présent message, ainsi que tout fichier qui y est joint, est (sont) envoyé(s) à l'intention exclusive de son ou (ses) destinataire(s); il est de nature confidentielle et peut faire l'objet d'une information privilégiée. Nous avisons toute personne autre que le destinataire prévu que tout examen, réacheminement, impression, copie, distribution ou toute autre utilisation de ce message et tout document joint est (sont) strictement interdit(s). Si vous n'êtes pas le destinataire prévu, veuillez en aviser immédiatement l'expéditeur par retour de courriel et supprimer ce message et tout document joint de votre système. Merci!
> > Gérez vos abonnements aux communications de BDC. <https://www.bdc.ca/fr/articles-outils/boite-outils-entrepreneur/publications/formulaire-abonnement?utm_medium=email&utm_source=signature&utm_campaign=email-footer-disclaimer_fr>
> > (Veuillez noter que vous continuerez de recevoir les messages électroniques non commerciaux nécessaires à votre relation d’affaires avec BDC.)
> >
> > 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, retransmission, 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. Thank you!
> > Manage your subscriptions to BDC messages. <https://www.bdc.ca/en/articles-tools/entrepreneur-toolkit/publications/subscribe?utm_medium=email&utm_source=signature&utm_campaign=email-footer-disclaimer_en>
> > (Please note that you will continue to receive non-commercial electronic messages necessary for your business relationship with BDC.)
>
Re: Integrate ActiveMQ classic version with Ldap for web console access
Posted by Matt Pavlovich <ma...@gmail.com>.
Hi Fabrice-
For ActiveMQ 5.x, the web console access is managed by Jetty in a separate password store. Following Jetty instructions for configuring LDAP and group permissions.
Ref: https://eclipse.dev/jetty/javadoc/jetty-9/org/eclipse/jetty/jaas/spi/LdapLoginModule.html
Note: For ActiveMQ 6.x (release vote is underway this week), the web and messaging layers are setup to share the same authentication source (aka JAAS realm), and the setup would be shared. Follow the ActiveMQ LDAP setup and both messaging and web layer services will share the same authentication source.
Hope this helps,
Matt Pavlovich
> On Nov 14, 2023, at 12:25 PM, HOUNGBE, Fabrice (MTL) <Fa...@bdc.ca.INVALID> wrote:
>
> Hi folks,
> Does anyone implement web console access integration with Ldap for ActiveMQ classic edition ?
> I know that the web console configuration is offered using jetty but Im having hard time updating jetty.xml to be able to integrate the web console access with Ldap.
> Any help will be really appreciated.
> Thks
>
> Fabrice Houngbe
> Spécialiste, Technologies | Technology Specialist
> T 514-807-6916 C 438-686-4037
>
> <http://www.bdc.ca/FR/Pages/accueil.aspx?utm_campaign=signature&utm_medium=email&utm_source=signature>
>
> bdc.ca <http://www.bdc.ca/FR/Pages/accueil.aspx?utm_campaign=signature&utm_medium=email&utm_source=signature>
>
> <http://www.bdc.ca/facebook> <http://www.bdc.ca/twitter> <http://www.bdc.ca/linkedin> <http://www.bdc.ca/youtube> <https://www.instagram.com/bdc_ca/>
>
>
> Information confidentielle : Le présent message, ainsi que tout fichier qui y est joint, est (sont) envoyé(s) à l'intention exclusive de son ou (ses) destinataire(s); il est de nature confidentielle et peut faire l'objet d'une information privilégiée. Nous avisons toute personne autre que le destinataire prévu que tout examen, réacheminement, impression, copie, distribution ou toute autre utilisation de ce message et tout document joint est (sont) strictement interdit(s). Si vous n'êtes pas le destinataire prévu, veuillez en aviser immédiatement l'expéditeur par retour de courriel et supprimer ce message et tout document joint de votre système. Merci!
> Gérez vos abonnements aux communications de BDC. <https://www.bdc.ca/fr/articles-outils/boite-outils-entrepreneur/publications/formulaire-abonnement?utm_medium=email&utm_source=signature&utm_campaign=email-footer-disclaimer_fr>
> (Veuillez noter que vous continuerez de recevoir les messages électroniques non commerciaux nécessaires à votre relation d’affaires avec BDC.)
>
> 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, retransmission, 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. Thank you!
> Manage your subscriptions to BDC messages. <https://www.bdc.ca/en/articles-tools/entrepreneur-toolkit/publications/subscribe?utm_medium=email&utm_source=signature&utm_campaign=email-footer-disclaimer_en>
> (Please note that you will continue to receive non-commercial electronic messages necessary for your business relationship with BDC.)
Re: Integrate ActiveMQ classic version with Ldap for web console access
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Fabrice,
Here's the steps to use LDAP for the ActiveMQ WebConsole (on ActiveMQ 5.x):
1. You have to add jetty-jaas jar in the lib/web folder, using the same
version as the Jetty artifacts already there (for instance
https://repo1.maven.org/maven2/org/eclipse/jetty/jetty-jaas/9.4.19.v20190610/jetty-jaas-9.4.19.v20190610.jar
)
2. You update conf/login.config to set "jetty" with LDAP login module:
jetty {
org.eclipse.jetty.jaas.spi.LdapLoginModule required
debug="true"
contextFactory="com.sun.jndi.ldap.LdapCtxFactory"
hostname="localhost"
port="10389"
bindDn="uid=admin,ou=system"
bindPassword="secret"
authenticationMethod="simple"
forceBindingLogin="true"
userBaseDn="ou=users,dc=example,dc=com"
userRdnAttribute="uid"
userIdAttribute="uid"
userPasswordAttribute="userPassword"
userObjectClass="inetOrgPerson"
roleBaseDn="ou=groups,dc=example,dc=com"
roleNameAttribute="cn"
roleMemberAttribute="member"
roleObjectClass="groupOfNames";
};
This example is a simple test I did using Apache DS locally on my machine.
3. In the conf/jetty.xml, I did a couple of minor updates in the security
handler:
....
<bean id="securityLoginService"
class="org.eclipse.jetty.jaas.JAASLoginService">
<property name="name" value="LDAP" />
<property name="loginModuleName" value="jetty" />
</bean>
....
<bean id="securityHandler"
class="org.eclipse.jetty.security.ConstraintSecurityHandler">
<property name="loginService" ref="securityLoginService" />
<property name="realmName" value="jetty" />
<property name="authenticator">
<bean
class="org.eclipse.jetty.security.authentication.BasicAuthenticator"
/>
</property>
<property name="constraintMappings">
<list>
<ref bean="adminSecurityConstraintMapping" />
<ref bean="securityConstraintMapping" />
</list>
</property>
<property name="handler" ref="secHandlerCollection" />
</bean>
...
4. (Optional) You can add some logger in conf/log4j.properties:
log4j.logger.org.eclipse.jetty=INFO
log4j.logger.org.eclipse.jetty.jaas=DEBUG
With that, you should see something like that in the activemq.log:
INFO | Attempting authentication: uid=jbonofre,ou=users,dc=example,dc=com
Please let me know if you need more help with this.
Regards
JB
On Tue, Nov 14, 2023 at 7:25 PM HOUNGBE, Fabrice (MTL)
<Fa...@bdc.ca.invalid> wrote:
> Hi folks,
>
> Does anyone implement web console access integration with Ldap for
> ActiveMQ classic edition ?
>
> I know that the web console configuration is offered using jetty but Im
> having hard time updating jetty.xml to be able to integrate the web console
> access with Ldap.
>
> Any help will be really appreciated.
>
> Thks
>
>
>
> *Fabrice Houngbe*
> Spécialiste, Technologies | Technology Specialist
> *T *514-807-6916 *C *438-686-4037
>
>
> <http://www.bdc.ca/FR/Pages/accueil.aspx?utm_campaign=signature&utm_medium=email&utm_source=signature>
>
> *bdc.ca
> <http://www.bdc.ca/FR/Pages/accueil.aspx?utm_campaign=signature&utm_medium=email&utm_source=signature>*
>
>
>
> <http://www.bdc.ca/facebook> <http://www.bdc.ca/twitter>
> <http://www.bdc.ca/linkedin> <http://www.bdc.ca/youtube>
> <https://www.instagram.com/bdc_ca/>
>
>
>
> *Information confidentielle :* Le présent message, ainsi que tout fichier
> qui y est joint, est (sont) envoyé(s) à l'intention exclusive de son ou
> (ses) destinataire(s); il est de nature confidentielle et peut faire
> l'objet d'une information privilégiée. Nous avisons toute personne autre
> que le destinataire prévu que tout examen, réacheminement, impression,
> copie, distribution ou toute autre utilisation de ce message et tout
> document joint est (sont) strictement interdit(s). Si vous n'êtes pas le
> destinataire prévu, veuillez en aviser immédiatement l'expéditeur par
> retour de courriel et supprimer ce message et tout document joint de votre
> système. Merci!
> Gérez vos abonnements aux communications de BDC.
> <https://www.bdc.ca/fr/articles-outils/boite-outils-entrepreneur/publications/formulaire-abonnement?utm_medium=email&utm_source=signature&utm_campaign=email-footer-disclaimer_fr>
> (Veuillez noter que vous continuerez de recevoir les messages
> électroniques non commerciaux nécessaires à votre relation d’affaires avec
> BDC.)
>
> *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, retransmission, 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. Thank you!
> Manage your subscriptions to BDC messages.
> <https://www.bdc.ca/en/articles-tools/entrepreneur-toolkit/publications/subscribe?utm_medium=email&utm_source=signature&utm_campaign=email-footer-disclaimer_en>
> (Please note that you will continue to receive non-commercial electronic
> messages necessary for your business relationship with BDC.)
>
>